LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46604: Apache ActiveMQ, Apache ActiveMQ Legacy OpenWire Module: Unbounded deserialization causes ActiveMQ to be vulnerable to a remote code execution (RCE) attack

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.

CriticalCVSS 10Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-46604 lets a remote attacker run commands through Apache ActiveMQ's OpenWire handling when reachable brokers or clients process manipulated serialized data. It is critical because exploitation requires network access but no authentication or user interaction. CISA lists it as known exploited, so internet-exposed or partner-facing messaging infrastructure needs urgent attention.

Executive priority

Treat this as an immediate remediation item for any ActiveMQ deployment. The combination of remote code execution, unauthenticated network attack path, CVSS 10.0, and CISA known-exploited status creates material business risk, especially for messaging systems that connect business applications or expose partner integrations.

Technical view

The Java OpenWire protocol marshaller can instantiate attacker-controlled class types on the classpath, leading to remote code execution in a Java-based broker or client. The issue is CWE-502 deserialization, CVSS 10.0, affecting Apache ActiveMQ and the Legacy OpenWire module. Apache recommends upgrading brokers and clients to fixed 5.15.16, 5.16.7, 5.17.6, or 5.18.3 releases.

Likely exposure

Exposure is most likely where Apache ActiveMQ brokers or Java OpenWire clients are reachable over networks, especially public, partner, or flat internal networks. Systems using org.apache.activemq:activemq-client or activemq-openwire-legacy should be inventoried. Evidence provided does not identify every downstream product beyond Apache, Debian, and NetApp advisory coverage.

Exploitation context

Active exploitation is supported by CISA KEV listing for CVE-2023-46604. Public references also include unauthenticated remote code execution material, increasing operational risk. The source bundle does not provide victim scope, attacker attribution, or safe detection signatures, so validation should focus on exposure, versions, and vendor guidance.

Researcher notes

Focus analysis on OpenWire exposure paths, broker and client versioning, and classpath-dependent impact. The provided sources support RCE through unsafe deserialization but do not provide complete downstream product coverage or authoritative detection logic. Avoid assuming only brokers are affected; Apache explicitly includes Java-based clients.

Mitigation direction

  • Upgrade brokers and clients to fixed Apache ActiveMQ versions named by Apache.
  • Prioritize internet-facing and partner-accessible OpenWire services first.
  • Restrict network access to OpenWire endpoints until upgrades are complete.
  • Check Debian, NetApp, and other vendor advisories for packaged fixes.
  • Confirm both broker and client dependencies are updated, not only servers.

Validation and detection

  • Inventory ActiveMQ brokers and Java OpenWire client dependencies.
  • Compare deployed versions against Apache fixed releases.
  • Identify OpenWire endpoints reachable from untrusted networks.
  • Review vendor package advisories for distro or appliance-specific status.
  • Check CISA KEV tracking for required remediation urgency.
Prepared
Reviewed
Confidence
high
Sources
6

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-46604 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2023-46604Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache ActiveMQorg.apache.activemq:activemq-client, 5.18.0, 5.17.0, 5.16.0, 0unaffected
Apache Software FoundationApache ActiveMQ Legacy OpenWire Moduleorg.apache.activemq:activemq-openwire-legacy, 5.18.0, 5.17.0, 5.16.0, 5.8.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.