spring-security-web-4.0.1.RELEASE.jar: 3 vulnerabilities (highest severity is: 7.5) reachable

[mend-local-app]

Vulnerable Library - spring-security-web-4.0.1.RELEASE.jar

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /pom.xml

Path to vulnerable library: /Users/alexmaybaum/.m2/repository/org/springframework/security/spring-security-web/4.0.1.RELEASE/spring-security-web-4.0.1.RELEASE.jar

Found in HEAD commit: d9961a50d4e1866631ab3050249381b0088bbbc6

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (spring-security-web version)	Remediation Possible**	Reachability
CVE-2016-9879	High	7.5	spring-security-web-4.0.1.RELEASE.jar	Direct	3.2.10,4.1.4,4.2.1.	✅	Reachable
CVE-2016-5007	High	7.5	spring-security-web-4.0.1.RELEASE.jar	Direct	org.springframework:spring-webmvc:4.3.0.RELEASE,org.springframework.security:spring-security-web:4.1.1.RELEASE,org.springframework.security:spring-security-config:4.1.1.RELEASE	✅	Reachable
CVE-2019-11272	High	7.3	spring-security-core-4.0.1.RELEASE.jar	Transitive	N/A*	❌	Reachable

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2016-9879

Vulnerable Library - spring-security-web-4.0.1.RELEASE.jar

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /pom.xml

Path to vulnerable library: /Users/alexmaybaum/.m2/repository/org/springframework/security/spring-security-web/4.0.1.RELEASE/spring-security-web-4.0.1.RELEASE.jar

Dependency Hierarchy:

• ❌ spring-security-web-4.0.1.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: d9961a50d4e1866631ab3050249381b0088bbbc6

Found in base branch: vp-rem

Reachability Analysis

This vulnerability is potentially reachable

com.visualpathit.account.service.UserDetailsServiceImpl (Application)
  -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
   -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
    -> org.springframework.security.config.annotation.web.builders.WebSecurity (Extension)
     -> org.springframework.security.web.FilterChainProxy (Extension)
      -> ❌ org.springframework.security.web.firewall.DefaultHttpFirewall (Vulnerable Component)

Vulnerability Details

An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath(), and getPathInfo(). Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified. Users of IBM WebSphere Application Server 8.5.x are known to be affected. Users of other containers that implement the Servlet specification may be affected.

Publish Date: 2017-01-06

URL: CVE-2016-9879

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: High
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9879

Release Date: 2017-01-06

Fix Resolution: 3.2.10,4.1.4,4.2.1.

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2016-5007

Vulnerable Library - spring-security-web-4.0.1.RELEASE.jar

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /pom.xml

Path to vulnerable library: /Users/alexmaybaum/.m2/repository/org/springframework/security/spring-security-web/4.0.1.RELEASE/spring-security-web-4.0.1.RELEASE.jar

Dependency Hierarchy:

• ❌ spring-security-web-4.0.1.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: d9961a50d4e1866631ab3050249381b0088bbbc6

Found in base branch: vp-rem

Reachability Analysis

This vulnerability is potentially reachable

com.visualpathit.account.service.UserDetailsServiceImpl (Application)
  -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
   -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
    -> org.springframework.security.config.annotation.web.configurers.ExpressionUrlAuthorizationConfigurer (Extension)
     -> ❌ org.springframework.security.web.access.expression.ExpressionBasedFilterInvocationSecurityMetadataSource (Vulnerable Component)

Vulnerability Details

Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.

Publish Date: 2017-05-25

URL: CVE-2016-5007

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: High
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://pivotal.io/security/cve-2016-5007

Release Date: 2017-05-25

Fix Resolution: org.springframework:spring-webmvc:4.3.0.RELEASE,org.springframework.security:spring-security-web:4.1.1.RELEASE,org.springframework.security:spring-security-config:4.1.1.RELEASE

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2019-11272

Vulnerable Library - spring-security-core-4.0.1.RELEASE.jar

spring-security-core

Library home page: http://spring.io/spring-security

Path to dependency file: /pom.xml

Path to vulnerable library: /Users/alexmaybaum/.m2/repository/org/springframework/security/spring-security-core/4.0.1.RELEASE/spring-security-core-4.0.1.RELEASE.jar

Dependency Hierarchy:

• spring-security-web-4.0.1.RELEASE.jar (Root Library)
  • ❌ spring-security-core-4.0.1.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: d9961a50d4e1866631ab3050249381b0088bbbc6

Found in base branch: vp-rem

Reachability Analysis

This vulnerability is potentially reachable

com.visualpathit.account.service.UserDetailsServiceImpl (Application)
  -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
   -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
    -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$3 (Extension)
     -> org.springframework.security.config.annotation.authentication.configurers.ldap.LdapAuthenticationProviderConfigurer (Extension)
      -> ❌ org.springframework.security.authentication.encoding.PlaintextPasswordEncoder (Vulnerable Component)

Vulnerability Details

Spring Security, versions 4.2.x up to 4.2.12, and older unsupported versions support plain text passwords using PlaintextPasswordEncoder. If an application using an affected version of Spring Security is leveraging PlaintextPasswordEncoder and a user has a null encoded password, a malicious user (or attacker) can authenticate using a password of "null".

Publish Date: 2019-06-26

URL: CVE-2019-11272

CVSS 3 Score Details (7.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11272

Release Date: 2019-06-26

Fix Resolution: org.springframework.security:spring-security-core:4.2.13.RELEASE

---

⛑️Automatic Remediation will be attempted for this issue.