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.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Pivotal Spring Framework — versions older unsupported versions are also affected, 4.2.x, 3.2.x
- Pivotal Spring Security — versions 4.1.0, 3.2.x, 4.0.x
- Pivotal Software Spring Framework — versions 3.2.0, 4.0.0, 4.1.0
- VMware Spring Framework — versions 3.2.1, 3.2.2, 3.2.3
- VMware Spring Security — versions 3.2.0, 3.2.1, 3.2.2
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 6 other repositories (ARPSyndicate/cvemon, audgks5551/springsecurity__2022_06_25, dfl0w/springsecurity__2022_06_25, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- www.securityfocus.com/bid/91687 (Third Party Advisory, VDB Entry, vdb-entry)
- pivotal.io/security/cve-2016-5007 (Vendor Advisory)
- www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html