CVE-2017-8045

Description

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 2.97% Top 15%
Vendor Advisory pivotal.io
Affected: n/a Spring AMQP Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7
Published at:
Updated at:

References

Link Tags
https://pivotal.io/security/cve-2017-8045 vendor advisory
http://www.securityfocus.com/bid/100936 third party advisory vdb entry

Frequently Asked Questions

What is the severity of CVE-2017-8045?
CVE-2017-8045 has been scored as a critical severity vulnerability.
How to fix CVE-2017-8045?
To fix CVE-2017-8045, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-8045 being actively exploited in the wild?
It is possible that CVE-2017-8045 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~3% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-8045?
CVE-2017-8045 affects n/a Spring AMQP Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.