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.
Published: 2021-10-28
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

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.

Subscriptions

Vmware Spring Advanced Message Queuing Protocol
cve-icon MITRE

Status: PUBLISHED

Assigner: vmware

Published:

Updated: 2024-08-03T18:30:24.007Z

Reserved: 2021-01-04T00:00:00.000Z

Link: CVE-2021-22097

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2021-10-28T16:15:08.023

Modified: 2024-11-21T05:49:31.417

Link: CVE-2021-22097

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses