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.
Project Subscriptions
| Vendors | Products |
|---|---|
|
Oracle
Subscribe
|
Application Testing Suite
Subscribe
Big Data Discovery
Subscribe
Communications Converged Application Server
Subscribe
Communications Diameter Signaling Router
Subscribe
Communications Performance Intelligence Center
Subscribe
Communications Services Gatekeeper
Subscribe
Enterprise Manager Ops Center
Subscribe
Goldengate For Big Data
Subscribe
Health Sciences Information Manager
Subscribe
Healthcare Master Person Index
Subscribe
Insurance Calculation Engine
Subscribe
Insurance Rules Palette
Subscribe
Primavera Gateway
Subscribe
Retail Back Office
Subscribe
Retail Central Office
Subscribe
Retail Customer Insights
Subscribe
Retail Integration Bus
Subscribe
Retail Open Commerce Platform
Subscribe
Retail Order Broker
Subscribe
Retail Point-of-sale
Subscribe
Retail Predictive Application Server
Subscribe
Retail Returns Management
Subscribe
Service Architecture Leveraging Tuxedo
Subscribe
Tape Library Acsls
Subscribe
|
|
Redhat
Subscribe
|
|
|
Vmware
Subscribe
|
Spring Framework
Subscribe
|
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0493 | 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. |
Github GHSA |
GHSA-4487-x383-qpph | Possible privilege escalation in org.springframework:spring-core |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sun, 13 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: dell
Published:
Updated: 2024-09-17T02:15:49.301Z
Reserved: 2017-12-06T00:00:00
Link: CVE-2018-1272
No data.
Status : Modified
Published: 2018-04-06T13:29:00.563
Modified: 2024-11-21T03:59:30.877
Link: CVE-2018-1272
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA