Apache ActiveMQ CVE-2019-0222: MQTT Frame Unmarshalling Vulnerability

activemq Updated 02 Oct 2025

Summary

28/03/2019
N/A
Yes i
High
7.5

CVE-2019-0222: In Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive. Affects activemq versions < 5.15.9-1. Fixed in 5.15.9-1. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache ActiveMQ is an open-source message broker that allows applications to communicate with each other using various messaging protocols. It provides reliable and scalable messaging services for distributed systems. ActiveMQ supports the MQTT protocol, which is widely used in IoT applications. However, a vulnerability has been discovered in ActiveMQ versions 5.0.0 to 5.15.8 that can lead to an Out of Memory exception and make the broker unresponsive when unmarshalling corrupt MQTT frames.

Vulnerability Detail

The vulnerability, identified as CVE-2019-0222, occurs when ActiveMQ attempts to process a corrupt MQTT frame. This can be exploited by an attacker to send specially crafted MQTT messages that trigger the Out of Memory exception. As a result, the broker becomes unresponsive and may require manual intervention to recover. The impact of this vulnerability can be severe, as it can lead to denial of service for the affected ActiveMQ instance.

How To Fix

Minimum fixed version

5.15.9-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade activemq

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 latest version of Apache ActiveMQ.

Conclusion

The Apache ActiveMQ CVE-2019-0222 vulnerability exposes ActiveMQ instances to the risk of denial of service due to an Out of Memory exception. It is crucial to upgrade to the latest version of ActiveMQ to mitigate this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for activemq →

Share this vulnerability

FAQ

Apache ActiveMQ is an open-source message broker that facilitates communication between applications using various messaging protocols.

The vulnerability can lead to an Out of Memory exception in ActiveMQ, making the broker unresponsive and causing denial of service.

ActiveMQ versions 5.0.0 to 5.15.8 are affected by this vulnerability.

No, there is no known workaround. It is recommended to upgrade to the latest version of ActiveMQ.

To fix this vulnerability, upgrade to Apache ActiveMQ version 5.15.9-1 or later.

Related vulnerabilities

Recent vulnerabilities recorded for activemq.

How To Fix

Minimum fixed version

5.15.9-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade activemq

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback