CyberSecBulletin
CVE-2023-46604Exploited in the wildNVD status: Analyzed

Apache ActiveMQ Deserialization of Untrusted Data

CVE-2023-46604 is a critical-severity deserialization of untrusted data vulnerability in Apache ActiveMQ from Apache, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 5.18.3, 5.17.6, 5.16.7 as the first without the flaw, so updating Apache ActiveMQ to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on November 2, 2023, which means attacks have been observed in the wild, including in ransomware campaigns.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Apache ActiveMQ to 5.18.3 or 5.17.6 or 5.16.7 or 5.15.16, whichever matches your release line, or a later version.
  2. Update Apache ActiveMQ Legacy OpenWire Module to 5.18.3 or 5.17.6 or 5.16.7 or 5.15.16, whichever matches your release line, or a later version.
  3. Update Activemq to 5.15.16 or 5.16.7 or 5.17.6 or 5.18.3, whichever matches your release line, or a later version.
  4. CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
  5. Read the advisory on activemq.apache.org for workarounds and exact fixed builds.
  6. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache ActiveMQ5.18.0 up to, but not including, 5.18.3; 5.17.0 up to, but not including, 5.17.6; 5.16.0 up to, but not including, 5.16.7; before 5.15.165.18.3, 5.17.6, 5.16.7, 5.15.16
ApacheApache ActiveMQ Legacy OpenWire Module5.18.0 up to, but not including, 5.18.3; 5.17.0 up to, but not including, 5.17.6; 5.16.0 up to, but not including, 5.16.7; 5.8.0 up to, but not including, 5.15.165.18.3, 5.17.6, 5.16.7, 5.15.16
ApacheActivemqbefore 5.15.16; 5.16.0 up to, but not including, 5.16.7; 5.17.0 up to, but not including, 5.17.6; 5.18.0 up to, but not including, 5.18.35.15.16, 5.16.7, 5.17.6, 5.18.3
ApacheActivemq Legacy Openwire Modulebefore 5.15.16; 5.16.0 up to, but not including, 5.16.7; 5.17.0 up to, but not including, 5.17.6; 5.18.0 up to, but not including, 5.18.35.15.16, 5.16.7, 5.17.6, 5.18.3
DebianDebian Linux10.0; 11.0Not stated
NetAppE-series Santricity Unified ManagerNot specified in the recordNot stated
NetAppE-series Santricity Web Services ProxyNot specified in the recordNot stated
NetAppSantricity Storage PluginNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.110.0CriticalCNA (apache.org)
CVSS 3.19.8CriticalNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How developers prevent this class of flaw

  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Explicitly define a final object() to prevent deserialization.

More Deserialization of Untrusted Data vulnerabilities (CWE-502)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Technical write-ups (may include proof of concept)

Other vulnerabilities in Apache ActiveMQ

All Apache ActiveMQ vulnerabilities

Recent Deserialization of Untrusted Data vulnerabilities

Spotted an error? Tell us.