pivotalsoftware spring-framework CVE-2018-1199 vulnerability in Pivotal Software and Other Products
Published on March 16, 2018

product logo product logo product logo product logo
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.

Vendor Advisory NVD


Products Associated with CVE-2018-1199

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2018-1199 are published in these products:

 
 
 
 
 
 
 

Affected Versions

Dell EMC Spring by Pivotal:

Exploit Probability

EPSS
1.51%
Percentile
80.93%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.