CVE-2016-5007
mediumpriority · track · 31EPSS 0.029 · 87 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5–7.5
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (76)
Products and version ranges known to be affected.
- pivotal software spring framework= 3.2.0nvdUScpe:2.3:a:pivotal_software:spring_framework:*:*:*:*:*:*:*:*
- pivotal software spring framework= 4.0.0nvdUScpe:2.3:a:pivotal_software:spring_framework:*:*:*:*:*:*:*:*
- pivotal software spring framework= 4.1.0nvdUScpe:2.3:a:pivotal_software:spring_framework:*:*:*:*:*:*:*:*
- pivotal software spring framework= 4.2.0nvdUScpe:2.3:a:pivotal_software:spring_framework:*:*:*:*:*:*:*:*
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-8crv-49fr-2h6jSpring Security and Spring Framework may not recognize certain paths that should be protected2018-10-17ghsa · osvUS
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 (as well as other unsupported versions) 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (17)
External citations — patches, advisories, analysis.
- http://www.hitachi.co.jp/Prod/comp/soft1/global/security/info/vuls/hitachi-sec-2019-108/index.htmlcnnvd
- http://www.ibm.com/support/docview.wsscnnvd
- http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.htmlcnnvd
- https://pivotal.io/security/cve-2016-5007cnnvd
- https://www.auscert.org.au/bulletins/76742cnnvd
- https://www.auscert.org.au/bulletins/79118cnnvd
- https://www.ibm.com/blogs/psirt/security-bulletin-ibm-security-guardium-is-affected-by-multiple-vulnerabilities-3/cnnvd
- https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.htmlcnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan