CVE-2018-1199

unknown
Published 2018-10-17 · Modified 2024-03-15
CVSS v3
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS v2
VIR risk

Description

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.

Predictions

Exploit likelihood
30%
Patch ETA

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

vendor Authored 2026-05-27

Vendor advisory: debian — https://security-tracker.debian.org/tracker/CVE-2018-1199

OS impact

OSVersionStatusFixed in
debian debianbookwormfixed4.3.14-1
debian debianbullseyefixed4.3.14-1
debian debianforkyfixed4.3.14-1
debian debiansidfixed4.3.14-1
debian debiantrixiefixed4.3.14-1

Package impact

EcosystemPackageVulnerableFixed
java Mavenorg.springframework.security:spring-security-core>=4.2.0,<4.2.44.2.4
java Mavenorg.springframework.security:spring-security-core>=5.0.0,<5.0.15.0.1
java Mavenorg.springframework:spring-core>=4.3.0,<4.3.144.3.14
java Mavenorg.springframework:spring-core>=5.0.0,<5.0.35.0.3
java Mavenorg.springframework.security:spring-security-core>=4.1.0,<4.1.54.1.5

References

Verify integrity in audit chain (admin only). AS-IS.