Spring Framework up to 4.3.14/5.0.4 Multipart Request access control

Summaryinfo

A vulnerability marked as critical has been reported in Spring Framework up to 4.3.14/5.0.4. The impacted element is an unknown function of the component Multipart Request Handler. This manipulation causes access control. This vulnerability appears as CVE-2018-1272. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Spring Framework up to 4.3.14/5.0.4. Affected by this vulnerability is an unknown code of the component Multipart Request Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 04/05/2018. The weakness was presented 04/06/2018 (Website). It is possible to read the advisory at pivotal.io. This vulnerability is known as CVE-2018-1272 since 12/06/2017. The attack can be launched remotely. A single authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 4.3.15 or 5.0.5 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103697†). See VDB-79791, VDB-95830, VDB-97118 and VDB-99028 for similar entries. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Spring Framework

Version

• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 4.3.5
• 4.3.6
• 4.3.7
• 4.3.8
• 4.3.9
• 4.3.10
• 4.3.11
• 4.3.12
• 4.3.13
• 4.3.14
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion