Description
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.
Remediation
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
Related Vulnerabilities
CVE-2019-10467 Vulnerability in maven package org.jenkins-ci.plugins:sonar-gerrit
CVE-2022-33891 Vulnerability in maven package org.apache.spark:spark-core_2.12
CVE-2023-33202 Vulnerability in maven package org.bouncycastle:bc-fips-debug
CVE-2019-19771 Vulnerability in npm package crpyto-js
CVE-2018-1308 Vulnerability in maven package org.apache.solr:solr-dataimporthandler