Skip to content
Fencer Intel
high 7.5

CVE-2019-0222 in the critical feed json

Improper Control of Generation of Code ('Code Injection') in org.apache.activemq:activemq-client

published 7y ago modified 4mo ago also GHSA-jpv3-g4cc-6vfx , EUVD-2019-0423

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.0%
EPSS 12.0% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

In Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive.

Patch / fix

  • maven org.apache.activemq:activemq-client 5.15.9
  • oracle goldengate_stream_analytics 19.1.0.0.1
  • activemq Debian 13, Debian 12 5.15.9-1
  • mqtt-client Debian 14, Debian 13, Debian 12 1.16-1

debian advisories DEBIAN-CVE-2019-0222

  • mqtt-client Ubuntu 20.04 LTS 1.14-1+deb10u1build0.20.04.1
  • mqtt-client Ubuntu Pro 16.04 LTS 1.10-1ubuntu0.1~esm1
  • mqtt-client Ubuntu Pro 18.04 LTS 1.14-1ubuntu0.18.04.1~esm1

ubuntu advisories UBUNTU-CVE-2019-0222

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-0222 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-0222 updated cvss 5.9

activemq: Corrupt MQTT frame can cause broker shutdown

  • Red Hat JBoss Developer Studio 11 activemq activemq
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7 activemq activemq
    affected: no fix planned “Will not fix”
  • Red Hat JBoss A-MQ 6 activemq activemq Red Hat JBoss Fuse 6 activemq activemq Red Hat JBoss Fuse Service Works 6 activemq activemq
    affected: no fix planned “Out of support scope”
  • Red Hat AMQ
    fixed: vendor fix RHSA-2020:0922
  • Red Hat AMQ 7.4.3
    fixed: vendor fix RHSA-2020:1445
  • Red Hat Decision Manager 7 activemq-artemis activemq-artemis Red Hat JBoss Data Grid 7 activemq-artemis activemq-artemis Red Hat JBoss Enterprise Application Platform 7 activemq-artemis activemq-artemis Red Hat Process Automation 7 activemq-artemis activemq-artemis Red Hat Single Sign-On 7 activemq-artemis activemq-artemis Red Hat Virtualization 4 eap7-activemq-artemis
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

12.03% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:activemq-client
>=5.0.0, <5.15.9
5.15.9

Affected products

  • Apache Apache ActiveMQ

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.