CVE-2018-1199
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.
How to fix
- vmware spring_framework4.3.14, 5.0.3 or later
- vmware spring_security4.1.5, 4.2.4, 5.0.1 or later
- org.springframework.security:spring-security-core4.2.4, 5.0.1, 4.1.5 or later
- org.springframework:spring-core4.3.14, 5.0.3 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| vmware spring_framework | 4.3.0 ≤ v < 4.3.14, 5.0.0 ≤ v < 5.0.3 | 4.3.14, 5.0.3 |
| vmware spring_security | 4.1.0 ≤ v < 4.1.5, 4.2.0 ≤ v < 4.2.4, 5.0.0 ≤ v < 5.0.1 | 4.1.5, 4.2.4, 5.0.1 |
| redhat fuse | 1.0 | — |
| oracle rapid_planning | 12.1, 12.2 | — |
| oracle retail_xstore_point_of_service | 7.1 | — |
| org.springframework.security:spring-security-coreMaven | 4.2.0 ≤ v < 4.2.4, 5.0.0 ≤ v < 5.0.1, 4.1.0 ≤ v < 4.1.5 | 4.2.4, 5.0.1, 4.1.5 |
| org.springframework:spring-coreMaven | 4.3.0 ≤ v < 4.3.14, 5.0.0 ≤ v < 5.0.3 | 4.3.14, 5.0.3 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.