Vulnerability in Pivotal Spring Framework

CVE-2016-5007

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

EPSS exploit prediction

EPSS: 0.028 (86.1th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 86th percentile — 86.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2016-5007: held from 0.028 to 0.028.

EPSS over last 30 days · oldest: 0.028 · newest: 0.028 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2016-5007?
CVE-2016-5007 is a high-severity vulnerability in Pivotal Spring Framework, classified under CWE-264. CVSS score: 7.5/10. Published 2017-05-25.
How severe is CVE-2016-5007?
High severity. CVSS v3 base score is 7.5 out of 10.
Is CVE-2016-5007 known to be exploited?
6 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.