Pivotal Spring AMQP up to 1.5.6/1.6.10/1.7.3 Message deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pivotal Spring AMQP up to 1.5.6/1.6.10/1.7.3 and classified as critical. Affected is an unknown function. Such manipulation as part of Message leads to deserialization. This vulnerability is listed as CVE-2017-8045. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Pivotal Spring AMQP up to 1.5.6/1.6.10/1.7.3. It has been rated as critical. Affected by this issue is an unknown code. The manipulation as part of a Message leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack.
The bug was discovered 09/19/2017. The weakness was presented 11/27/2017 by Man Yue Mo with Semmle (Website). The advisory is shared for download at pivotal.io. This vulnerability is handled as CVE-2017-8045 since 04/21/2017. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 69 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.5.7, 1.6.11 or 1.7.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 100936†). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 1.5.0
- 1.5.1
- 1.5.2
- 1.5.3
- 1.5.4
- 1.5.5
- 1.5.6
- 1.6.0
- 1.6.1
- 1.6.2
- 1.6.3
- 1.6.4
- 1.6.5
- 1.6.6
- 1.6.7
- 1.6.8
- 1.6.9
- 1.6.10
- 1.7.0
- 1.7.1
- 1.7.2
- 1.7.3
License
Website
- Vendor: https://pivotal.io/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Spring AMQP 1.5.7/1.6.11/1.7.4
Timeline
04/21/2017 🔍09/19/2017 🔍
09/19/2017 🔍
11/27/2017 🔍
11/27/2017 🔍
11/27/2017 🔍
12/10/2019 🔍
Sources
Vendor: pivotal.ioAdvisory: pivotal.io
Researcher: Man Yue Mo
Organization: Semmle
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-8045 (🔍)
GCVE (CVE): GCVE-0-2017-8045
GCVE (VulDB): GCVE-100-109988
SecurityFocus: 100936 - Spring AMQP CVE-2017-8045 Remote Code Execution Vulnerability
Entry
Created: 11/27/2017 16:25Updated: 12/10/2019 17:49
Changes: 11/27/2017 16:25 (60), 12/10/2019 17:49 (6)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.