CVE-2024-27137 Apache Cassandra
| Affected software | Apache Cassandra |
|---|---|
| Severity | 5.3 Medium CVSS 3.1 |
| Fixed in | 5.0.3, 4.1.8, 4.0.15 |
| Weakness | Improper authentication (CWE-287) |
| Published | 4 Feb 2025 |
| Updated | 17 Jun 2026 |
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.
CWE-668
Exploitation status
No public exploit
No exploit has been reported in the sources we check. Published a year ago.
Exploitation status
- CISA KEV not listed
- VulnCheck KEV not listed
- CISA Vulnrichment exploitation: none
- Indexed PoC none indexed
- EPSS 0.28% chance in 30 days
Waratek protection
Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.
A public code fix exists.
- Protection none
- Action unverified
- Review automated Upstream data
- Record active
| Decided by | Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory |
|---|---|
| Finding | This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain. |
Affected software and releases
Maven packages
Affected and fixed versions, from OSV.dev| Package | Introduced | Fixed | Last affected |
|---|---|---|---|
org.apache.cassandra:cassandra-all |
5.0-beta1 | 5.0.3 |
unbounded |
org.apache.cassandra:cassandra-all |
4.1.0 | 4.1.8 |
unbounded |
org.apache.cassandra:cassandra-all |
4.0.2 | 4.0.15 |
unbounded |
Products and versions
2 products, 10 version entries| Source | Vendor | Product | Scheme | Affected versions |
|---|---|---|---|---|
| nvd | apache | cassandra | generic | ≥ 4.0.2 and < 4.0.15 · ≥ 4.1.0 and < 4.1.8 · 5.0.0 · 5.0.0:beta1 · 5.0.0:rc1 · 5.0.0:rc2 · > 5.0.0 and < 5.0.3 |
| osv | org.apache.cassandra | cassandra-all | generic | ≥ 4.0.2 and < 4.0.15 · ≥ 4.1.0 and < 4.1.8 · ≥ 5.0 and < 5.0.3 |
References
Timeline
Timeline
| Published | 2025-02-04 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-06-17 | NVD's own last-modified date for this record. |