CVE-2016-5007
N/A
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Pivotal | Spring Security | 3.2.x | affected |
| Pivotal | Spring Security | 4.0.x | affected |
| Pivotal | Spring Security | 4.1.0 | affected |
| Pivotal | Spring Framework | 3.2.x | affected |
| Pivotal | Spring Framework | 4.0.x | affected |
| Pivotal | Spring Framework | 4.1.x | affected |
| Pivotal | Spring Framework | 4.2.x | affected |
| Pivotal | Spring Framework | older unsupported versions are also affected | affected |
Weaknesses
- Security Control Bypass
ADP Enrichment
CVE Program Container
Additional References
- http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- http://www.securityfocus.com/bid/91687
- https://pivotal.io/security/cve-2016-5007
- https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
References
- http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- http://www.securityfocus.com/bid/91687
- https://pivotal.io/security/cve-2016-5007
- https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.