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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: dell
Published: 2018-03-16T20:00:00Z
Updated: 2024-09-16T16:13:09.643Z
Reserved: 2017-12-06T00:00:00
Link: CVE-2018-1199
Vulnrichment
No data.
NVD
Status : Modified
Published: 2018-03-16T20:29:00.430
Modified: 2023-11-07T02:55:51.583
Link: CVE-2018-1199
Redhat