Memory Allocation with Excessive Size Value Affecting org.apache.activemq:activemq-client package, versions [,5.16.8)[5.17.0,5.17.7)[5.18.0,5.18.7)[6.0.0,6.1.6)


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.37% (58th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JAVA-ORGAPACHEACTIVEMQ-10074037
  • published8 May 2025
  • disclosed7 May 2025
  • creditUnknown

Introduced: 7 May 2025

NewCVE-2025-27533  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

Upgrade org.apache.activemq:activemq-client to version 5.16.8, 5.17.7, 5.18.7, 6.1.6 or higher.

Overview

org.apache.activemq:activemq-client is a high performance Apache 2.0 licensed Message Broker and JMS 1.1 implementation.

Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value during the unmarshalling of OpenWire commands, where the size value of buffers is not properly validated. An attacker can deplete process memory and cause service disruptions by sending crafted messages.

Workaround

Existing users may implement mutual TLS to mitigate the risk on affected brokers.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

CVSS Base Scores

version 4.0
version 3.1