Skip to content
Fencer Intel
critical 9.8

CVE-2017-8045 json

Deserialization of Untrusted Data in Spring AMQP

published 2017-11-27 8 y ago modified 2026-06-17 4 mo ago also GHSA-vqqg-xgv7-cf68 , EUVD-2022-5412

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.6%
EPSS 3.6% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.amqp:spring-amqp 1.5.7, 1.6.11, 1.7.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-8045 updated cvss 8.1

springframework-amqp: Message.toString() deserializes java without a whitelist

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.55% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.amqp:spring-amqp
<1.5.7
>=1.6.0, <1.6.11
>=1.7.0, <1.7.4
1.5.7
1.6.11
1.7.4

Affected products

  • n/a Spring AMQP Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.