CVE-2018-1199

Severity: medium (CVSS 5.3 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 2.9% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2018-03-16 · updated 2026-06-17
Weakness: CWE-20

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.

Affected products

Oracle Corporation Rapid Planning: 12.1, 12.2
Oracle Corporation Retail Xstore Point of Service: 7.1
Red Hat Fuse: 1.0
Spring Framework: from 4.3.0 before 4.3.14; from 5.0.0 before 5.0.3 — fixed in 4.3.14, 5.0.3
Spring Security: from 4.1.0 before 4.1.5; from 4.2.0 before 4.2.4; from 5.0.0 before 5.0.1 — fixed in 4.1.5, 4.2.4, 5.0.1
Dell EMC Spring by Pivotal: from spring Security 4.1.0 through 4.1.4, 4.2.0 - 4.2.3, 5.0.0; from Spring Framework 5.0.0 through 5.0.2, 4.3.0 - 4.3.13; Older unmaintained versions of Spring Security & Spring Framework were not analyzed and may be impacted

How to fix

Upgrade to a fixed version: Spring Framework 4.3.14, 5.0.3; Spring Security 4.1.5, 4.2.4, 5.0.1. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2018-1199 or the next vulnerability affects your stack