Skip to content

Apache Cassandra: unrestricted deserialization of JMX authentication credentials

Moderate severity GitHub Reviewed Published Feb 4, 2025 to the GitHub Advisory Database • Updated Feb 4, 2025

Package

maven org.apache.cassandra:cassandra-all (Maven)

Affected versions

>= 5.0-beta1, < 5.0.3
>= 4.1.0, < 4.1.8
>= 4.0.2, < 4.0.15

Patched versions

5.0.3
4.1.8
4.0.15

Description

In Apache Cassandra it is possible for a local attacker without access to the Apache Cassandra process or configuration files to manipulate the RMI registry to perform a man-in-the-middle attack and capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and perform unauthorized operations.

This is same vulnerability that CVE-2020-13946 was issued for, but the Java option was changed in JDK10.

This issue affects Apache Cassandra from 4.0.2 through 5.0.2 running Java 11.

Operators are recommended to upgrade to a release equal to or later than 4.0.15, 4.1.8, or 5.0.3 which fixes the issue.

References

Published by the National Vulnerability Database Feb 4, 2025
Published to the GitHub Advisory Database Feb 4, 2025
Reviewed Feb 4, 2025
Last updated Feb 4, 2025

Severity

Moderate

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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Weaknesses

CVE ID

CVE-2024-27137

GHSA ID

GHSA-rgfx-7p65-3ff4

Source code

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