GHSA-crg9-44h2-xw35 BIT-activemq-2023-46604 CVE-2023-46604
Apache ActiveMQ is vulnerable to Remote Code Execution
Critical
Known exploited
Maven
- Severity
- 10.0 / 10
- Critical · CVSS 3.1
- Exploit chance (EPSS)
- 99.99%
- Chance of exploitation in the next 30 days. Higher than 99.99% of scored vulnerabilities.
- Known exploited
- Yes
- In CISA's catalog since Nov 2, 2023
- Weakness
- CWE-502 Deserialization of Untrusted Data
- Fix
- Available
- 2 packages have a fixed version
Exploited in the wild. Apache ActiveMQ Deserialization of Untrusted Data Vulnerability (Apache ActiveMQ). Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Due for U.S. federal agencies by Nov 23, 2023. Known to be used in ransomware campaigns.
Description
Apache ActiveMQ is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker with network access to a broker to run arbitrary shell commands by manipulating serialized class types in the OpenWire protocol to cause the broker to instantiate any class on the classpath.
Users are recommended to upgrade to version 5.15.16, 5.16.7, 5.17.6, or 5.18.3, which fixes this issue.
Affected versions
Maven
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.apache.activemq:activemq-client Maven → 5.15.16
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>activemq-client</artifactId><version>5.15.16</version></dependency>- gradle
implementation("org.apache.activemq:activemq-client:5.15.16")
org.apache.activemq:activemq-openwire-legacy Maven → 5.15.16
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>activemq-openwire-legacy</artifactId><version>5.15.16</version></dependency>- gradle
implementation("org.apache.activemq:activemq-openwire-legacy:5.15.16")
Severity breakdown
CVSS 3.1 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H/E:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
- Exploit maturity
- H
Weakness
CWE-502: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How to prevent it
- Architecture and Design, Implementation: 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.
- Implementation: 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.
- Implementation: Explicitly define a final object() to prevent deserialization.
- Architecture and Design, Implementation: Make fields transient to protect them from deserialization. An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
- Implementation: Avoid having unnecessary types or gadgets (a sequence of instances and method invocations that can self-execute during the deserialization process, often found in libraries) available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are constantly being discovered, so this alone is not a sufficient mitigation.
- Architecture and Design, Implementation: Employ cryptography of the data or code for protection. However, it's important to note that it would still be client-side security. This is risky because if the client is compromised then the security implemented on the client (the cryptography) can be bypassed.
- Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
References
Advisories
Fixes and patches
- github.com/apache/activemq/pull/1098
- github.com/apache/activemq/commit/80089f9f476afab7d976f5fc37c5ab4aa0c2139d
- github.com/apache/activemq/commit/22442b2385b1000312aec3d19e510131d595a5fc
- github.com/apache/activemq/commit/958330df26cf3d5cdb63905dc2c6882e98781d8f
- github.com/apache/activemq/commit/9905e2a5bf9862a049f94ce0a2465b0c7ad52436
- github.com/apache/activemq/commit/d0ccdd31544ada83185554c87c7aa141064020f0
Packages
Other links
- activemq.apache.org/security-advisories.data/CVE-2023-46604-announcement.txt
- activemq.apache.org/security-advisories.data/CVE-2023-46604
- issues.apache.org/jira/browse/AMQ-9370
- openwall.com/lists/oss-security/2023/10/27/5
- openwall.com/lists/oss-security/2023/10/27/5
- packetstormsecurity.com/files/175676/Apache-ActiveMQ-Unauthenticated-Remote-Code-Execution.html
- lists.debian.org/debian-lts-announce/2023/11/msg00013.html
- packetstormsecurity.com/files/175676/Apache-ActiveMQ-Unauthenticated-Remote-Code-Execution.html
- security.netapp.com/advisory/ntap-20231110-0010
- seclists.org/fulldisclosure/2024/Apr/18
- cisa.gov/known-exploited-vulnerabilities-catalog
- lists.debian.org/debian-lts-announce/2024/10/msg00027.html
Timeline
- Published
- Added to CISA's Known Exploited Vulnerabilities catalog
- Remediation due for U.S. federal agencies
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-rxqh-fc23-gxp2 Improper Input Validation in Apache ActiveMQ | Critical Known exploited | Also affects org.apache.activemq:activemq-client |
| GHSA-5568-6qcg-g7fx Apache ActiveMQ: Denial of Service via Out of Memory vulnerability | High | Also affects org.apache.activemq:activemq-client |
| GHSA-h2h4-5m64-m273 Apache ActiveMQ: Improper validation and restriction of a classpath path name | Medium | Also affects org.apache.activemq:activemq-client |
| GHSA-whxr-3p84-rf3c Apache ActiveMQ: Unchecked buffer length can cause excessive memory allocation | High | Also affects org.apache.activemq:activemq-client |
| GHSA-p358-58jj-hp65 Improper Authentication in Apache ActiveMQ | Medium | Also affects org.apache.activemq:activemq-client |
| GHSA-mfhr-3xmc-r2gg Improper Neutralization of Input During Web Page Generation in Apache ActiveMQ | Medium | Also affects org.apache.activemq:activemq-client |
| GHSA-3wfj-vh84-732p Improper Neutralization of Special Elements used in an OS Command in Apache ActiveMQ | High | Also affects org.apache.activemq:activemq-client |
| GHSA-9cvr-8xq4-2m73 Improper Neutralization of Input During Web Page Generation in Apache ActiveMQ | Medium | Also affects org.apache.activemq:activemq-client |
Credits: nmarcoccio, sunSUNQ
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor