pivotalsoftware spring-framework CVE-2016-5007 in Pivotal Software and VMware Products
Published on May 25, 2017

product logo product logo
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.

NVD


Products Associated with CVE-2016-5007

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2016-5007 are published in these products:

 
 
 

Affected Versions

Pivotal Spring Security: Pivotal Spring Framework:

Exploit Probability

EPSS
0.16%
Percentile
36.05%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.