Skip to content
Noroxi
CVE-2018-1199· NVD / CVE Program· CNA dell

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

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.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Mar 16, 2018
Updated
Jun 16, 2026
EPSS
2.9% · 87th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.9%

Affected systems

VendorProduct
vmwarespring framework
vmwarespring security
redhatfuse
oraclerapid planning
oracleretail xstore point of service

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • oracle rapid planning12.1
  • oracle rapid planning12.2
  • oracle retail xstore point of service7.1
  • redhat fuse1.0
  • vmware spring framework4.3.0 and later · before 4.3.14
  • vmware spring framework5.0.0 and later · before 5.0.3
  • vmware spring security5.0.0 and later · before 5.0.1
  • vmware spring security4.2.0 and later · before 4.2.4
  • vmware spring security4.1.0 and later · before 4.1.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.

  • Dell EMC Spring by Pivotal

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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libspring-javabefore 4.3.14-14.3.14-1
Mavenorg.springframework:spring-corefrom 4.3.0 · before 4.3.144.3.14
Mavenorg.springframework:spring-corefrom 5.0.0 · before 5.0.35.0.3
Mavenorg.springframework.security:spring-security-corefrom 4.1.0 · before 4.1.54.1.5
Mavenorg.springframework.security:spring-security-corefrom 4.2.0 · before 4.2.44.2.4
Mavenorg.springframework.security:spring-security-corefrom 5.0.0 · before 5.0.15.0.1

Other highest-scoring records for the same primary product.

  • CVE-2022-22965A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.KEV
    99Now
  • CVE-2018-1270Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose
    62This week
  • CVE-2020-5398RFD Attack via "Content-Disposition" Header Sourced from Request Input by Spring MVC or Spring WebFlux Application
    57Plan
  • CVE-2018-1275Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose
    56Plan
  • CVE-2016-1000027Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untru
    49Plan
  • CVE-2026-59313Server Sent Event stream corruption in Spring MVC functional web framework
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libspring-java4.3.14-1 · Debian:12Package registry (OSV)
Maven:org.springframework:spring-core4.3.14Package registry (OSV)
Maven:org.springframework:spring-core5.0.3Package registry (OSV)
Maven:org.springframework.security:spring-security-core4.1.5Package registry (OSV)
Maven:org.springframework.security:spring-security-core4.2.4Package registry (OSV)
Maven:org.springframework.security:spring-security-core5.0.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records