dbcve.org
Spring Advanced Message Queuing ProtocolFramework / library · VMware

CVE-2021-22095

MEDIUM · 6.5 CVSS v3.1 Published 2021-11-30
Fix available
A fix is available. Upgrade to 2.2.19 / 2.3.11 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Spring AMQP versions 2.2.0 - 2.2.19 and 2.3.0 - 2.3.11, the Spring AMQP Message object, in its toString() method, will create a new String object from the message body, regardless of its size. This can cause an OOM Error with a large message

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Spring AMQP versions 2.2.0-2.2.19 and 2.3.0-2.3.11, the Message.toString() method unconditionally creates a new String object from the message body regardless of size. This can exhaust heap memory when processing large messages, causing denial of service.

MitigationUpgrade Spring AMQP to version 2.2.20 or 2.3.12 or later, which includes the fix for this unbounded String allocation in toString(). Consider implementing message size limits at the application layer as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Advanced Message Queuing ProtocolFramework / library
Affected:>= 2.2.0, < 2.2.19>= 2.3.0, < 2.3.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring AMQP library version
    Locate the spring-amqp JAR file in your application's classpath or dependency management (Maven pom.xml, Gradle build.gradle, or the JAR's MANIFEST.MF). Check the version number against 2.2.0-2.2.19 or 2.3.0-2.3.11.
    Affected if The installed version falls within 2.2.0-2.2.19 or 2.3.0-2.3.11.
  2. Verify application code calls Message.toString()
    Search your codebase for invocations of Message.toString(), logger.debug(msg), logger.info(msg), or similar logging statements where a Spring AMQP Message object would be logged or converted to String.
    Affected if Code directly or indirectly invokes toString() on org.springframework.amqp.core.Message objects.
  3. Check message listener processing patterns
    Inspect MessageListener implementations, @RabbitListener methods, or any consumer code that processes incoming messages. Look for patterns that serialize, log, or convert the full Message object to String.
    Affected if Message processing code serializes or logs the entire Message object, triggering toString().

You are affected if your application runs Spring AMQP version 2.2.0-2.2.19 or 2.3.0-2.3.11 and processes messages in a way that calls toString() on large Message objects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.19 / 2.3.11 or later
Fixed in 2.2.192.3.11
Interim mitigation

Upgrade Spring AMQP to version 2.2.20 or 2.3.12 or later, which includes the fix for this unbounded String allocation in toString(). Consider implementing message size limits at the application layer as a defense-in-depth measure.

Recommended fix High confidence

Spring AMQP 2.2.19 or 2.3.11 (or later stable release)

  1. Identify the current Spring AMQP version in your project dependency management (e.g., pom.xml, build.gradle)
  2. If using version 2.2.x, upgrade to version 2.2.19 or later
  3. If using version 2.3.x, upgrade to version 2.3.11 or later
  4. Update the version in your build configuration file (e.g., pom.xml, build.gradle)
  5. Rebuild the project to fetch the updated dependency
  6. Run tests to verify message handling functionality, especially with large messages
  7. Deploy the updated application
Caveat Minor/patch version upgrades typically contain only bug fixes; review release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Advanced Message Queuing Protocol Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22095 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data