Apache ActiveMQ: Unchecked buffer length can cause excessive memory allocation
Apache Software Foundation Apache ActiveMQ
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.activemq:activemq-openwire-legacy Maven |
|
|
Apache Software Foundation Apache ActiveMQ
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.activemq:activemq-openwire-legacy Maven |
|
|
| org.apache.activemq:activemq-client Maven |
|
|
Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ.
During unmarshalling of OpenWire commands the size value of buffers was not properly validated which could lead to excessive memory allocation and be exploited to cause a denial of service (DoS) by depleting process memory, thereby affecting applications and services that rely on the availability of the ActiveMQ broker when not using mutual TLS connections. This issue affects Apache ActiveMQ: from 6.0.0 before 6.1.6, from 5.18.0 before 5.18.7, from 5.17.0 before 5.17.7, before 5.16.8. ActiveMQ 5.19.0 is not affected.
Users are recommended to upgrade to version 6.1.6+, 5.19.0+, 5.18.7+, 5.17.7, or 5.16.8 or which fixes the issue.
Existing users may implement mutual TLS to mitigate the risk on affected brokers.
From the CVE record · apache
Apache ActiveMQ does not properly validate buffer sizes when unmarshalling OpenWire commands. An attacker who can send OpenWire commands to a broker not using mutual TLS can exhaust process memory, causing a denial of service. The input does not specify whether other authentication is required.
Operators of Apache ActiveMQ brokers and users of the Maven packages activemq-openwire-legacy or activemq-client should check versions before 5.16.8, 5.17.0–5.17.6, 5.18.0–5.18.6, and 6.0.0–6.1.5.