cve.bz

CVE-2018-1199 Improper Input Validation

5.3 mediumEPSS 2.8%Fix available

Medium (5.3). EPSS 2.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.security:spring-security-core 4.1.5, 4.2.4, 5.0.1.

On this page
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.

Severity

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
EPSS
2.8% (unchanged from 2.8% a week ago; 2.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 87th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-1199 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-1199?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-1199?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-1199 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vmware:spring_frameworkfrom 4.3.0 before 4.3.14
vmware:spring_frameworkfrom 5.0.0 before 5.0.3
vmware:spring_securityfrom 4.1.0 before 4.1.5
vmware:spring_securityfrom 4.2.0 before 4.2.4
vmware:spring_securityfrom 5.0.0 before 5.0.1
redhat:fuse1.0
oracle:rapid_planning12.1
oracle:rapid_planning12.2
oracle:retail_xstore_point_of_service7.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v596-fwhq-8x48Mavenorg.springframework.security:spring-security-core>=4.2.0 <4.2.44.2.4
GHSA-v596-fwhq-8x48Mavenorg.springframework.security:spring-security-core>=5.0.0 <5.0.15.0.1
GHSA-v596-fwhq-8x48Mavenorg.springframework:spring-core>=4.3.0 <4.3.144.3.14
GHSA-v596-fwhq-8x48Mavenorg.springframework:spring-core>=5.0.0 <5.0.35.0.3
GHSA-v596-fwhq-8x48Mavenorg.springframework.security:spring-security-core>=4.1.0 <4.1.54.1.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libspring-java4.3.14-1DEBIAN-CVE-2018-1199
UbuntuPro:14.04:LTS, Pro:16.04:LTSlibspring-javano fix listedUBUNTU-CVE-2018-1199

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

As a general precaution, users are encouraged to separate public and private resources. For example, separating static resources and mapping them to /resources/public/** and /resources/private/** is preferred to having one common root with mixed public and private resource content underneath.

ProductPackageStateAdvisory
Red Hat Fuse Intergration Services 2.0 based on Fuse 6.3 R7Fixed 2018-08-14RHSA-2018:2405
Red Hat Enterprise Linux 8springframeworkNot affected
Red Hat Fuse 7springAffected
Red Hat JBoss A-MQ 6springNot affected
Red Hat JBoss BRMS 5springNot affected
Red Hat JBoss Data Virtualization 6springNot affected
Red Hat JBoss Enterprise Application Platform 5jbosswebNot affected
Red Hat JBoss Enterprise Application Platform 6jbosswebNot affected
Red Hat JBoss Enterprise Application Platform 7undertow-coreNot affected
Red Hat JBoss Enterprise Web Server 2tomcatNot affected
Red Hat JBoss Fuse 6springNot affected
Red Hat JBoss Fuse Integration Service 2springAffected
Red Hat JBoss Fuse Service Works 6springNot affected
Red Hat JBoss Portal 6springNot affected
Red Hat JBoss SOA Platform 5springNot affected
Red Hat JBoss Web Server 3tomcatNot affected
Red Hat Mobile Application Platform 4springNot affected
Red Hat OpenShift Enterprise 3millicoreNot affected
Red Hat OpenStack Platform 10 (Newton)opendaylightWill not fix
Red Hat OpenStack Platform 11 (Ocata)opendaylightWill not fix
3 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2018-1199.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON