MediumGHSA-v596-fwhq-8x48CVE-2018-1199

Improper Input Validation in org.springframework.security:spring-security-core, org.springframework.security:spring-security-core , and org.springframework:spring-core

Published 17 Oct 2018 · Updated 15 Mar 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
>=4.2.0 <4.2.4
Fixed in
4.2.4
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.4 -DforceVersion=true
Affected
>=5.0.0 <5.0.1
Fixed in
5.0.1
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.0.1 -DforceVersion=true
Affected
>=4.3.0 <4.3.14
Fixed in
4.3.14
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=4.3.14 -DforceVersion=true
Affected
>=5.0.0 <5.0.3
Fixed in
5.0.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=5.0.3 -DforceVersion=true
Affected
>=4.1.0 <4.1.5
Fixed in
4.1.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=4.1.5 -DforceVersion=true

Details

Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, 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. 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. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.

Is GHSA-v596-fwhq-8x48 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.