Skip to content

Remote code execution in Apache ActiveMQ

Critical severity GitHub Reviewed Published Feb 9, 2022 to the GitHub Advisory Database • Updated Mar 14, 2024

Package

maven org.apache.activemq:activemq-parent (Maven)

Affected versions

= 5.15.12

Patched versions

5.15.13

Description

A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to RMIConnectorServer, instead of the map that contains the authentication credentials, it leaves ActiveMQ open to the following attack - A remote client could create a javax.management.loading.MLet MBean and use it to create new MBeans from arbitrary URLs, at least if there is no security manager. In other words, a rogue remote client could make your Java application execute arbitrary code. Mitigation - Upgrade to Apache ActiveMQ 5.15.13

References

Published by the National Vulnerability Database Sep 10, 2020
Reviewed Apr 5, 2021
Published to the GitHub Advisory Database Feb 9, 2022
Last updated Mar 14, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.447%
(75th percentile)

Weaknesses

CVE ID

CVE-2020-11998

GHSA ID

GHSA-wqfh-9m4g-7x6x

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.