CVE-2018-1272
CVE-2018-1272 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, provide client-side support for multipart requests. When Spring MVC or Spring WebFlux server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.
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
3%
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)
References
10 on the record
- www.securityfocus.com/bid/103697
vdb-entry, x_refsource_BID
- access.redhat.com/errata/RHSA-2018:2669
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
- www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
x_refsource_MISC
Elsewhere on this site
- spring by pivotalevery CVE for this vendor
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.