Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

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…

Medium5.3EPSS 2.8%
Published
Updated
Reserved
Assigned by
dell

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.

Scores

CVSS scores of CVE-2018-1199, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
2.8% · top 13% of all CVEs (4 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.

Weakness

Affected products

  • Dell EMC · Spring by Pivotal

    • affected spring Security 4.1.0 - 4.1.4, 4.2.0 - 4.2.3, 5.0.0
    • affected Spring Framework 5.0.0 - 5.0.2, 4.3.0 - 4.3.13
    • affected Older unmaintained versions of Spring Security & Spring Framework were not analyzed and may be impacted

Affected packages

From reviewed advisories of the GitHub Advisory Database.

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2018-1199 badge
[![CVE-2018-1199](https://trackcve.app/badge/CVE-2018-1199.svg)](https://trackcve.app/cve/CVE-2018-1199)

Record last updated .