Spring Framework up to 4.3.17/5.0.6 JSONP Cross-Domain 7pk security

Summaryinfo

A vulnerability has been found in Spring Framework up to 4.3.17/5.0.6 and classified as critical. This impacts an unknown function of the component JSONP. The manipulation leads to 7pk security (Cross-Domain). This vulnerability is listed as CVE-2018-11040. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Spring Framework up to 4.3.17/5.0.6. It has been rated as critical. This issue affects an unknown part of the component JSONP. The manipulation with an unknown input leads to a 7pk security vulnerability (Cross-Domain). Using CWE to declare the problem leads to CWE-254. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Spring Framework, versions 5.0.x prior to 5.0.7 and 4.3.x prior to 4.3.18 and older unsupported versions, allows web applications to enable cross-domain requests via JSONP (JSON with Padding) through AbstractJsonpResponseBodyAdvice for REST controllers and MappingJackson2JsonView for browser requests. Both are not enabled by default in Spring Framework nor Spring Boot, however, when MappingJackson2JsonView is configured in an application, JSONP support is automatically ready to use through the "jsonp" and "callback" JSONP parameters, enabling cross-domain requests.

The bug was discovered 06/14/2018. The weakness was presented 06/25/2018 (Website). It is possible to read the advisory at pivotal.io. The identification of this vulnerability is CVE-2018-11040 since 05/14/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1211 according to MITRE ATT&CK.

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

Upgrading to version 4.3.18 or 5.0.7 eliminates this vulnerability.

See VDB-119842 for similar entry. Statistical analysis made it clear that VulDB provides the best quality 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
• 4.3.15
• 4.3.16
• 4.3.17
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion