CVE-2022-23913: Apache ActiveMQ Artemis DoS via uncontrolled memory consumption

CVE-2022-23913 · Severity: high · CVSS 7.5 · Published 2022-02-06

Apache ActiveMQ Artemis is a high-performance message broker used to facilitate communication between different software applications. A vulnerability in how it handles incoming data packets allows an attacker to crash the service by forcing it to consume excessive amounts of memory. This can lead to a denial-of-service (DoS) condition, disrupting business operations and message delivery.

Vendors: Maven.

Quick answers

Is CVE-2022-23913 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-23913 being exploited in the wild.
How severe is CVE-2022-23913?
High severity, with a CVSS score of 7.5, published 6 February 2022.
Which products and versions are affected?
org.apache.activemq:artemis-core-client (Maven) < 2.19.1, ECOSYSTEM:introduced=0,fixed=2.19.1.
Is there a fix for CVE-2022-23913?
Yes. org.apache.activemq:artemis-core-client (Maven): upgrade to 2.19.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2022-23913 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2022-23913?
Check whether you run org.apache.activemq:artemis-core-client (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.activemq:artemis-core-client (Maven): upgrade to 2.19.1 or later
    # set org.apache.activemq:artemis-core-client to 2.19.1 in your pom.xml or build.gradle

Technical details

A vulnerability exists in Apache ActiveMQ Artemis (specifically within the artemis-core-client and XidCodecSupport) due to improper validation of user-supplied lengths during memory allocation. An unauthenticated remote attacker can send a handcrafted packet with a large 'claimed size' value for XID data. The application attempts to allocate a byte array based on this value without sufficient boundary checks against the actual buffer capacity, leading to an OutOfMemoryError (OOM) and subsequent JVM crash. This issue is addressed in versions 2.19.1 and 2.20.0 by implementing defensive checks in the safeReadBytes method.

Affected products

  • Apache ActiveMQ Artemis < 2.19.1, < 2.20.0

Identifiers

  • CVE-2022-23913
  • GHSA-pr38-qpxm-g88x

Timeline

  • 2022-02-04: advisory: NVD published CVE-2022-23913
  • 2022-02-06: advisory: GitHub Advisory published
  • 2021-12-03: patched: Fix merged into main branch

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.