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.
References
Link | Resource |
---|---|
https://pivotal.io/security/cve-2016-5007 | Vendor Advisory |
http://www.securityfocus.com/bid/91687 | Third Party Advisory VDB Entry |
http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html | |
https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html |
Configurations
Configuration 1 (hide)
|
Information
Published : 2017-05-25 10:29
Updated : 2022-04-11 10:18
NVD link : CVE-2016-5007
Mitre link : CVE-2016-5007
JSON object : View
CWE
CWE-264
Permissions, Privileges, and Access Controls
Products Affected
pivotal_software
- spring_framework
vmware
- spring_security
- spring_framework