Skip to content
Fencer Vulns
medium 6.5

CVE-2021-22097 json

Deserialization of Untrusted Data in Spring AMQP

published 2021-10-28 5 y ago modified 2026-06-17 4 mo ago also GHSA-fx7f-rjqj-52pj , EUVD-2022-3851

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

In Spring AMQP versions 2.2.0 - 2.2.18 and 2.3.0 - 2.3.10, the Spring AMQP Message object, in its toString() method, will deserialize a body for a message with content type application/x-java-serialized-object. It is possible to construct a malicious java.util.Dictionary object that can cause 100% CPU usage in the application if the toString() method is called.

Patch / fix

  • maven org.springframework.amqp:spring-amqp 2.2.19, 2.3.11

Exploit prediction

1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 6.8 AV:N/AC:L/Au:S/C:N/I:N/A:C
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.amqp:spring-amqp
>=2.2.0, <2.2.19
>=2.3.0, <2.3.11
2.2.19
2.3.11

Affected products

  • n/a Spring AMQP

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns 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.