CVE-2016-5007 High Severity Vulnerability detected by WhiteSource

[mend-bolt-for-github]

CVE-2016-5007 - High Severity Vulnerability

Vulnerable Libraries - spring-webmvc-3.2.4.RELEASE.jar, spring-security-web-3.2.4.RELEASE.jar, spring-security-config-3.2.4.RELEASE.jar

spring-webmvc-3.2.4.RELEASE.jar

Spring Web MVC

path: /html_test/10_webgoat-container-7.0.1/WEB-INF/lib/spring-webmvc-3.2.4.RELEASE.jar,2/repository/org/springframework/spring-webmvc/3.2.4.RELEASE/spring-webmvc-3.2.4.RELEASE.jar

Library home page: https://github.com/SpringSource/spring-framework

Dependency Hierarchy:

• ❌ spring-webmvc-3.2.4.RELEASE.jar (Vulnerable Library)

spring-security-web-3.2.4.RELEASE.jar

null

path: /html_test/10_webgoat-container-7.0.1/WEB-INF/lib/spring-security-web-3.2.4.RELEASE.jar,2/repository/org/springframework/security/spring-security-web/3.2.4.RELEASE/spring-security-web-3.2.4.RELEASE.jar

Dependency Hierarchy:

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

spring-security-config-3.2.4.RELEASE.jar

null

path: /html_test/10_webgoat-container-7.0.1/WEB-INF/lib/spring-security-config-3.2.4.RELEASE.jar,2/repository/org/springframework/security/spring-security-config/3.2.4.RELEASE/spring-security-config-3.2.4.RELEASE.jar

Dependency Hierarchy:

• ❌ spring-security-config-3.2.4.RELEASE.jar (Vulnerable Library)

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-12-31

Fix Resolution: Users of affected versions should apply the following mitigation: To address these issues comprehensively Spring Security provides URL authorization that can delegate pattern matching to the Spring Framework. To take advantage of this option applications should upgrade to and and use the . Starting with Spring Framework 4.3.0+ the is configured with set to “false” which aligns with Spring Security. Therefore simply using Spring Framework 4.3.0+ can eliminate some causes of path matching inconsistencies. Users of Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x can use the or the to set property of to “false”. In addition, applications should always complement URL-based authorization with additional authorization at the business layer of the application using one of Spring Security’s mechanisms such as adding annotations.

---

Step up your Open Source Security Game with WhiteSource here