Authorization Bypass in Spring Security
Published 15 Sept 2020 · Updated 16 Apr 2024
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
- <3.1.7
- Fixed in
- 3.1.7
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=3.1.7 -DforceVersion=true- Affected
- >=3.2.0 <3.2.5
- Fixed in
- 3.2.5
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=3.2.5 -DforceVersion=trueDetails
When using Spring Security's CAS Proxy ticket authentication a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request.
This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed.
If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.
Mitigation
Users of affected versions should apply the following mitigation:
- Users of 3.2x should upgrade to 3.2.5 or later
- Users of 3.1.x should upgrade to 3.1.7 or later
Credit
This issue was identified by David Ohsie and brought to our attention by the CAS Development team.
Is GHSA-wmv4-5w76-vp9g 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
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.