HighGHSA-v35c-49j6-q8hqCVE-2016-9879

Security Constraint Bypass in Spring Security

Published 15 Sept 2020 · Updated 29 Nov 2024

Is your project on an affected org.springframework.security:spring-security-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<3.2.10.RELEASE
Fixed in
3.2.10.RELEASE
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=3.2.10.RELEASE -DforceVersion=true
Affected
>=4.0.0.RELEASE <4.1.4.RELEASE
Fixed in
4.1.4.RELEASE
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=4.1.4.RELEASE -DforceVersion=true
Affected
>=4.2.0.RELEASE <4.2.1.RELEASE
Fixed in
4.2.1.RELEASE
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-core -DdepVersion=4.2.1.RELEASE -DforceVersion=true

Details

Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification (see below). Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed.

Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath() and getPathInfo() [1].

Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified.

Users of IBM WebSphere Application Server 8.5.x are known to be affected.

Users of other containers that implement the Servlet specification may be affected.

[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=25015

Affected Pivotal Products and Versions

Severity is high unless otherwise noted.

  • Spring Security 3.2.0 - 3.2.9
  • Spring Security 4.0.x - 4.1.3
  • Spring Security 4.2.0
  • Older unsupported versions are also affected

Mitigation

Adopting one of the following mitigations will protect against this vulnerability.

  • Use a Servlet container known not to include path parameters in the return values for getServletPath() and getPathInfo()
  • Upgrading to Spring Security 3.2.10, 4.1.4 or 4.2.1 will reject the request with a RequestRejectedException if the presence of an encoded "/" is detected. Note: If you wish to disable this feature it can be disabled by setting the DefaultHttpFirewall.allowUrlEncodedSlash = true. However, disabling this feature will mean applications are vulnerable (in containers that return path parameters in getServletPath() or getPathInfo()).

Credit

The issue was identified by Shumpei Asahara & Yuji Ito from NTT DATA Corporation and responsibly reported to Pivotal.

Is GHSA-v35c-49j6-q8hq 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
All 31 advisories for org.springframework.security:spring-security-core

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.