CVE-2018-1271
CVE-2018-1271 Vulnerability Analysis & Exploit Intelligence
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 configure Spring MVC to serve static resources (e.g. CSS, JS, images). When static resources are served from a file system on Windows (as opposed to the classpath, or the ServletContext), a malicious user can send a request using a specially crafted URL that can lead a directory traversal attack.
Published Updated Sources: cvelistV5, dell
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
35%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Weakness & attack patterns
- CWE-22
References
11 on the record
- www.securityfocus.com/bid/103699
vdb-entry, x_refsource_BID
- access.redhat.com/errata/RHSA-2018:2669
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:2939
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:1320
vendor-advisory, x_refsource_REDHAT
- www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
x_refsource_CONFIRM
- www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
x_refsource_CONFIRM
- www.oracle.com/security-alerts/cpujul2020.html
x_refsource_MISC
- www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
x_refsource_CONFIRM
Elsewhere on this site
- spring by pivotalevery CVE for this vendor
- CWE-22other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.