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…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.8% (FIRST EPSS); higher than 86.7% of all records.
- 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.
- Fixed version: libspring-java (Debian:12) 4.3.14-1; org.springframework:spring-core (Maven) 4.3.14, 5.0.3; org.springframework.security:spring-security-core (Maven) 4.1.5, 4.2.4, 5.0.1.
Low priority for now. Upgrade to libspring-java (Debian:12) 4.3.14-1; org.springframework:spring-core (Maven) 4.3.14, 5.0.3; org.springframework.security:spring-security-core (Maven) 4.1.5, 4.2.4, 5.0.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 16, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.8% · 86th percentile
- CWE
- CWE-20
Report tools
Action score
22
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring framework | cpe:2.3:a:vmware:spring_framework |
| vmware | spring security | cpe:2.3:a:vmware:spring_security |
| redhat | fuse | cpe:2.3:a:redhat:fuse |
| oracle | rapid planning | cpe:2.3:a:oracle:rapid_planning |
| oracle | retail xstore point of service | cpe:2.3:a:oracle:retail_xstore_point_of_service |
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
Affected versions · NVD (9)
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libspring-java | before 4.3.14-1 | 4.3.14-1 |
| Maven | org.springframework:spring-core | from 4.3.0 · before 4.3.14 | 4.3.14 |
| Maven | org.springframework:spring-core | from 5.0.0 · before 5.0.3 | 5.0.3 |
| Maven | org.springframework.security:spring-security-core | from 4.1.0 · before 4.1.5 | 4.1.5 |
| Maven | org.springframework.security:spring-security-core | from 4.2.0 · before 4.2.4 | 4.2.4 |
| Maven | org.springframework.security:spring-security-core | from 5.0.0 · before 5.0.1 | 5.0.1 |
Same product
vmware: all recordsOther 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.KEV99Now
- 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 Application56Plan
Published before and after this one in the same product
- ← EarlierCVE-2011-2894Oct 4, 2011 · Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize…30Monitor
- ← EarlierCVE-2015-5211May 25, 2017 · Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to…39Monitor
- Later →CVE-2018-1271Apr 6, 2018 · Spring 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…32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libspring-java | 4.3.14-1 · Debian:12 | Package registry (OSV) |
| Maven:org.springframework:spring-core | 4.3.14 | Package registry (OSV) |
| Maven:org.springframework:spring-core | 5.0.3 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 4.1.5 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 4.2.4 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 5.0.1 | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- lists.apache.org/thread.html/4ed49b103f64a0cecb38064f26cbf1389afc12124653da2d35166dbe%40%3Cissues.activemq.apache.org%3E
- lists.apache.org/thread.html/ab825fcade0b49becfa30235b3d54f4a51bb74ea96b6c9adb5d1378c%40%3Cissues.activemq.apache.org%3E
- lists.apache.org/thread.html/dcf8599b80e43a6b60482607adb76c64672772dc2d9209ae2170f369%40%3Cissues.activemq.apache.org%3E
- pivotal.io/security/cve-2018-1199
- www.oracle.com/security-alerts/cpujul2020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.