Skip to content

Apache ActiveMQ Artemis Uncontrolled Resource Consumption (DoS)

High severity GitHub Reviewed Published Feb 6, 2022 to the GitHub Advisory Database • Updated Sep 25, 2023

Package

maven org.apache.activemq:artemis-core-client (Maven)

Affected versions

< 2.19.1

Patched versions

2.19.1

Description

In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could partially disrupt availability (DoS) through uncontrolled resource consumption of memory.

References

Published by the National Vulnerability Database Feb 4, 2022
Published to the GitHub Advisory Database Feb 6, 2022
Reviewed Feb 8, 2022
Last updated Sep 25, 2023

Severity

High

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
None
Integrity
None
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:N/I:N/A:H

EPSS score

0.186%
(57th percentile)

Weaknesses

CVE ID

CVE-2022-23913

GHSA ID

GHSA-pr38-qpxm-g88x

Source code

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