Spring Security and Spring Framework may not recognize certain paths that should be protected
Published 17 Oct 2018 · Updated 2 Dec 2024
Is your project on an affected org.springframework:spring-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <4.3.1
- Fixed in
- 4.3.1
mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=4.3.1 -DforceVersion=true- Affected
- <4.1.1
- Fixed in
- 4.1.1
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=4.1.1 -DforceVersion=trueDetails
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.
Is GHSA-8crv-49fr-2h6j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework:spring-core, and gives you the command that fixes it.
More advisories for org.springframework:spring-core
- LowCVE-2026-41848Spring Framework Denial of Service via AntPathMatcher · 9 Jun 2026
- HighCVE-2025-41249Spring Framework annotation detection mechanism may result in improper authorization · 16 Sept 2025
- HighCVE-2024-22233Spring Framework server Web DoS Vulnerability · 22 Jan 2024
- MediumCVE-2021-22096Improper Output Neutralization for Logs in Spring Framework · 24 May 2022
- HighCVE-2011-2730Improper Neutralization of Directives in Dynamically Evaluated Code in Spring Framework · 17 May 2022
- MediumCVE-2011-2894Spring Framework and Spring Security vulnerable to Deserialization of Untrusted Data · 14 May 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2016-5007
- Linkgithub.com/spring-projects/spring-security/issues/3964
- Linkgithub.com/spring-projects/spring-framework/commit/a30ab30e4e9ae021fdda04e9abfc228476b846b5
- Linkgithub.com/spring-projects/spring-security/commit/e4c13e3c0ee7f06f59d3b43ca6734215ad7d8974
- Advisorygithub.com/advisories/GHSA-8crv-49fr-2h6j
- Linkpivotal.io/security/cve-2016-5007
- Linkwww.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
- Linkwww.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- Linkwww.securityfocus.com/bid/91687
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.