WaratekVRT Sign in

CVE-2018-1199

Affected software5 products, listed below
Severity5.3 Medium CVSS 3.1 2 scores
Fixed in4.2.4, 5.0.1, 4.1.5
WeaknessImproper input validation (CWE-20)
Published16 Mar 2018
Updated17 Jun 2026

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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 8 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS 2.8% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: spring-projects/spring-framework 554662e.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

CVSS

5.3 MEDIUM v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 5.3 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N NVD Primary published
CVSS 2.0 5.0 none AV:N/AC:L/Au:N/C:P/I:N/A:N NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.springframework.security:spring-security-core 4.2.0 4.2.4 unbounded
org.springframework.security:spring-security-core 5.0.0 5.0.1 unbounded
org.springframework:spring-core 4.3.0 4.3.14 unbounded
org.springframework:spring-core 5.0.0 5.0.3 unbounded
org.springframework.security:spring-security-core 4.1.0 4.1.5 unbounded

Products and versions

7 products, 14 version entries
SourceVendorProductSchemeAffected versions
nvd oracle rapid planning generic 12.1 · 12.2
nvd oracle retail xstore point of service generic 7.1
osv org.springframework spring-core generic ≥ 4.3.0 and < 4.3.14 · ≥ 5.0.0 and < 5.0.3
osv org.springframework.security spring-security-core generic ≥ 4.1.0 and < 4.1.5 · ≥ 4.2.0 and < 4.2.4 · ≥ 5.0.0 and < 5.0.1
nvd redhat fuse generic 1.0
nvd vmware spring framework generic ≥ 4.3.0 and < 4.3.14 · ≥ 5.0.0 and < 5.0.3
nvd vmware spring security generic ≥ 4.1.0 and < 4.1.5 · ≥ 4.2.0 and < 4.2.4 · ≥ 5.0.0 and < 5.0.1

References

URLTags
https://github.com/spring-projects/spring-framework/commit/554662ebab87af97ba25d0c9f5449c7acda8df9c WEB
https://github.com/spring-projects/spring-framework/commit/73a81f98d40eb6f5faa91aceb868db53fae2a94b WEB
https://github.com/spring-projects/spring-framework/commit/e6e6b8f4adcad99d133de97fcfac5ae5dd14153c WEB
https://github.com/spring-projects/spring-security/commit/0eef5b4b425ab42b9fa0fde1a3f36a37b92558f WEB
https://github.com/spring-projects/spring-security/commit/65da28e4bf62f58fb130ba727cbbd621b44a36d WEB
https://github.com/spring-projects/spring-security/commit/cb8041ba67635edafcc934498ef82707157fd22 WEB
https://access.redhat.com/errata/RHSA-2018:2405 WEB
https://github.com/advisories/GHSA-v596-fwhq-8x48 ADVISORY
https://lists.apache.org/thread.html/4ed49b103f64a0cecb38064f26cbf1389afc12124653da2d35166dbe@%3Cissues.activemq.apache.org%3E WEB
https://lists.apache.org/thread.html/ab825fcade0b49becfa30235b3d54f4a51bb74ea96b6c9adb5d1378c@%3Cissues.activemq.apache.org%3E WEB

Timeline

Published2018-03-16By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.