CVE-2021-22097

Published Oct 28, 2021 CVSS 3.1 · 6.5 Medium EPSS 1.1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2022-3851 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.
Github GHSA Github GHSA GHSA-fx7f-rjqj-52pj Deserialization of Untrusted Data in Spring AMQP
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 3, 2024, 6:30 PM
Reserved
Jan 4, 2021, 12:00 AM
Status
Modified
Published
Oct 28, 2021, 4:15 PM
Modified
Jun 17, 2026, 3:36 AM