cve.bz

CVE-2023-46604 Apache ActiveMQ Deserialization of Untrusted Data Vulnerability

9.8 criticalKEVExploitEPSS >99.9%Fix available

Critical (9.8) in Apache ActiveMQ. In CISA KEV since 2023-11-02, with known ransomware use. EPSS >99.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.activemq:activemq-client 5.15.16, 5.16.7, 5.17.6.

On this page
The Java OpenWire protocol marshaller is vulnerable to Remote Code Execution. This vulnerability may allow a remote attacker with network access to either a Java-based OpenWire broker or client to run arbitrary shell commands by manipulating serialized class types in the OpenWire protocol to cause either the client or the broker (respectively) to instantiate any class on the classpath. Users are recommended to upgrade both brokers and clients to version 5.15.16, 5.16.7, 5.17.6, or 5.18.3 which fixes this issue.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
>99.9% (unchanged from >99.9% a week ago; 99.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2023-11-02, due 2023-11-23, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-02-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-46604 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-46604?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-46604?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-46604 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache ActiveMQfrom 5.18.0 before 5.18.3
Apache Software Foundation Apache ActiveMQfrom 5.17.0 before 5.17.6
Apache Software Foundation Apache ActiveMQfrom 5.16.0 before 5.16.7
Apache Software Foundation Apache ActiveMQbefore 5.15.16
Apache Software Foundation Apache ActiveMQ Legacy OpenWire Modulefrom 5.18.0 before 5.18.3
Apache Software Foundation Apache ActiveMQ Legacy OpenWire Modulefrom 5.17.0 before 5.17.6
Apache Software Foundation Apache ActiveMQ Legacy OpenWire Modulefrom 5.16.0 before 5.16.7
Apache Software Foundation Apache ActiveMQ Legacy OpenWire Modulefrom 5.8.0 before 5.15.16

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-client<5.15.165.15.16
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-client>=5.16.0 <5.16.75.16.7
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-client>=5.17.0 <5.17.65.17.6
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-client>=5.18.0 <5.18.35.18.3
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-openwire-legacy>=5.8.0 <5.15.165.15.16
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-openwire-legacy>=5.16.0 <5.16.75.16.7
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-openwire-legacy>=5.17.0 <5.17.65.17.6
GHSA-crg9-44h2-xw35Mavenorg.apache.activemq:activemq-openwire-legacy>=5.18.0 <5.18.35.18.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian10activemq5.15.16-0+deb10u1DLA-3657-1
Debian11activemq5.16.1-1+deb11u1DLA-3936-1
Debian12activemq5.17.2+dfsg-2+deb12u1DEBIAN-CVE-2023-46604 DSA-5798-1
Debian13activemq5.17.6+dfsg-1DEBIAN-CVE-2023-46604
Ubuntu22.04:LTSactivemq5.16.1-1ubuntu0.1UBUNTU-CVE-2023-46604 USN-7268-1
UbuntuPro:16.04:LTSactivemq5.13.2+dfsg-2ubuntu0.1~esm1UBUNTU-CVE-2023-46604 USN-6910-1
UbuntuPro:18.04:LTSactivemq5.15.8-2~18.04.1~esm1UBUNTU-CVE-2023-46604 USN-6910-1
UbuntuPro:20.04:LTSactivemq5.15.11-1ubuntu0.1~esm1UBUNTU-CVE-2023-46604 USN-6910-1
UbuntuPro:22.04:LTSactivemq5.16.1-1ubuntu0.1~esm1UBUNTU-CVE-2023-46604 USN-6910-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

If the openwire protocol IS NOT in use, system operators can disable the OpenWire protocol which removes most risk of this vulnerability being exploited. If OpenWire IS being used, see the Mitigations section for potential options to reduce your attack surface.

* How to determine if an AMQ 7 system is affected:

Check in the broker.xml configuration file. Notice the presence of **OPENWIRE** in the following snippet which indicates a vulnerable configuration.

~~~

<acceptor name="artemis">tcp://localhost:####?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,**OPENWIRE**;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>

~~~

* How to determine if an AMQ 7 for OpenShift system is affected:

Get the `ActivemqArtemis` CR yaml and review the acceptor protocol and see if the following entry is present: `(default, all, Openwire)` which indicates the system is vulnerable.

* How to determine if a Fuse 6 system is affected:

By default Fuse 6 includes and enables ActiveMQ Broker. So unless this has been manually disabled, every Fuse 6 system is affected by this vulnerability.

* How to determine if a Fuse 7 system is affected:

Fuse 7 itself is not vulnerable. By default it ships the vulnerable activemq-client jar, however it does not instantiate an ActiveMQ broker. If this feature (connect to an external ActiveMQ Broker) were manually configured, it would make it vulnerable.

* How to determine if a Fuse Online system is affected:

Syndesis, an Integration Platform As A Service part of Fuse Online which runs on top of Openshift, does not use activemq code. Also, it doesn't instantiate a broker with Openwire protocol enabled, which makes it not vulnerable to this CVE.

Red Hat's mitigation

In affected systems, it may be possible to mitigate some of the risks from this vulnerability. However this mitigation cannot eliminate all risks; the only complete resolution is to apply software updates. On systems where the broker is exposed to the public network, use firewall rules to restrict the transport ports and enable SSL to protect this "Transport".

ProductPackageStateAdvisory
AMQ 6.3 openshift container imageFixed 2023-11-09RHSA-2023:6877
AMQ Broker 7.10.5Fixed 2023-11-09RHSA-2023:6878
AMQ Broker 7.11.4activemq-openwireFixed 2023-11-09RHSA-2023:6879
Red Hat Fuse 7.12.1activemq-openwireFixed 2023-11-15RHSA-2023:7247
Red Hat Fuse/AMQ 6.3.20activemq-openwireFixed 2023-11-09RHSA-2023:6849
RHEL-7 based Middleware Containersjboss-amq-6/amq63-openshift:1.4-50Fixed 2023-11-09RHSA-2023:6866
Red Hat JBoss Fuse Service Works 6activemq-openwireOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-46604.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-274-01Armatura LLC Armatura One2026-10-01Communications, Critical Manufacturing, Energy, Transportation SystemsArmatura LLC Armatura One: <4.7.2, Armatura LLC Armatura One (USA): <4.6.1none listed
ICSA-25-044-14Siemens Opcenter Intelligence2025-02-11Critical ManufacturingOpcenter Intelligencenone listed
ICSA-24-130-03Delta Electronics InfraSuite Device Master2024-05-09Critical ManufacturingDelta Electronics InfraSuite Device Master: <=1.0.10none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

6 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Nuclei template Apache ActiveMQ - Remote Code Execution
  • Emerging Threats Open ET EXPLOIT Successful Apache ActiveMQ Remote Code Execution (CVE-2023-46604) sid 2049385
  • Emerging Threats Open ET EXPLOIT Apache ActiveMQ Remote Code Execution Attempt (CVE-2023-46604) sid 2049045
  • Emerging Threats Open ET INFO Remote Spring Application XML Configuration Containing ProcessBuilder Downloaded sid 2049046
  • Emerging Threats Open ET INFO Apache ActiveMQ Instance - Vulnerable to CVE-2023-46604 - Remote Instance sid 2049008
  • Emerging Threats Open ET INFO Apache ActiveMQ Instance - Vulnerable to CVE-2023-46604 - Local Instance sid 2049009

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON