MediumGHSA-q3v6-hm2v-pw99CVE-2024-38827
Spring Framework has Authorization Bypass for Case Sensitive Comparisons
Published 2 Dec 2024 · Updated 10 Sept 2026
Is your project on an affected org.springframework.security:spring-security-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <5.7.14
- Fixed in
- 5.7.14
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=5.7.14 -DforceVersion=true- Affected
- >=5.8.0 <5.8.16
- Fixed in
- 5.8.16
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=5.8.16 -DforceVersion=true- Affected
- >=6.0.0 <6.0.14
- Fixed in
- 6.0.14
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.0.14 -DforceVersion=true- Affected
- >=6.1.0 <6.1.12
- Fixed in
- 6.1.12
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.1.12 -DforceVersion=true- Affected
- >=6.2.0 <6.2.8
- Fixed in
- 6.2.8
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.2.8 -DforceVersion=true- Affected
- >=6.3.0 <6.3.5
- Fixed in
- 6.3.5
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=6.3.5 -DforceVersion=trueDetails
The usage of String.toLowerCase() and String.toUpperCase() has some Locale dependent exceptions that could potentially result in authorization rules not working properly.
Is GHSA-q3v6-hm2v-pw99 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.security:spring-security-core, and gives you the command that fixes it.
More advisories for org.springframework.security:spring-security-core
- LowCVE-2026-22746Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider · 22 Apr 2026
- MediumCVE-2026-22751Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured · 21 Apr 2026
- MediumCVE-2025-22234Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide · 22 Jan 2026
- HighCVE-2025-41248Spring Security annotation detection mechanism has authorization bypass · 16 Sept 2025
- CriticalCVE-2025-41232Spring Security authorization bypass for method security annotations on private methods · 21 May 2025
- MediumCVE-2025-22223Spring Security Vulnerable to Authorization Bypass via Security Annotations · 24 Mar 2025
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-38827
- Linkgithub.com/spring-projects/spring-framework/issues/33708
- Linkgithub.com/spring-projects/spring-framework/issues/34232
- Linkgithub.com/spring-projects/spring-framework/commit/11d4272ff48b4a4dabc4b28dfbff0364a4204bc9
- Packagegithub.com/spring-projects/spring-security
- Linksecurity.netapp.com/advisory/ntap-20250124-0007
- Linkspring.io/security/cve-2024-38827
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.