CVE-2019-0222: Code Injection in org.apache.activemq:activemq-client
Summary
CVE-2019-0222: Improper Control of Generation of Code ('Code Injection') in org.apache.activemq:activemq-client. Affects org.apache.activemq:activemq-client versions >= 5.0.0, < 5.15.9. Fixed in 5.15.9. How to fix ↓
Also tracked for
- activemq · Debian:11
The same CVE-2019-0222 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The org.apache.activemq:activemq-client package is a part of Apache ActiveMQ, which is an open-source message broker that implements the Java Message Service (JMS) API. It provides reliable messaging between distributed applications and supports various messaging protocols. The activemq-client module is responsible for the client-side functionality of ActiveMQ, allowing applications to connect to and interact with the message broker.
Vulnerability Detail
This vulnerability, identified as CVE-2019-0222, is an instance of improper control of code generation, also known as code injection. In Apache ActiveMQ versions 5.0.0 to 5.15.8, a flaw exists in the unmarshalling process of MQTT frames. If a corrupt MQTT frame is unmarshalled by the broker, it can lead to an Out of Memory exception, causing the broker to become unresponsive. This vulnerability can be exploited by an attacker to disrupt the message broker's functionality and potentially impact the availability of messaging services.
How To Fix
Latest published version: 6.3.2 as of 23 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
5.15.9
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the patched version of Apache ActiveMQ.
Conclusion
The code injection vulnerability in the org.apache.activemq:activemq-client package can lead to an Out of Memory exception in Apache ActiveMQ versions 5.0.0 to 5.15.8. Upgrading to version 5.15.9 or later is recommended to fix this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.activemq:activemq-client →
FAQ
Apache ActiveMQ is an open-source message broker that implements the Java Message Service (JMS) API. It provides reliable messaging between distributed applications and supports various messaging protocols.
The activemq-client module is responsible for the client-side functionality of Apache ActiveMQ. It allows applications to connect to and interact with the message broker.
Code injection is a vulnerability that occurs when untrusted data is used to generate or execute code. In this case, the vulnerability allows an attacker to inject malicious code into the Apache ActiveMQ broker, potentially leading to an Out of Memory exception and unresponsiveness.
Exploiting this vulnerability can result in the unresponsiveness of the Apache ActiveMQ broker, impacting the availability of messaging services. It can disrupt communication between distributed applications relying on the message broker.
To mitigate this vulnerability, it is crucial to upgrade to Apache ActiveMQ version 5.15.9 or later, which includes a fix for the code injection issue. By applying the patched version, the vulnerability can be addressed.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.activemq:activemq-client.
