Skip to content

Vendor

org.apache.cassandra vulnerabilities

13 published CVES affecting org.apache.cassandra, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
13
Critical
2
High
6
Medium
5
Low
0
Unscored
0
CISA KEV
0
Atom feed of org.apache.cassandra alerts

Products

Latest org.apache.cassandra CVEs

Newest publication first

  1. MediumCVSS 5.5 EPSS 0.17%

    Sensitive Information Leak in cqlsh in Apache Cassandra 4.0 allows access to sensitive information, like passwords, from previously executed cqlsh command via ~/.cassandra/cqlsh_history local file access. Users are recommended to upgrade to version 4.0.20, which fixes this issue....

  2. CriticalCVSS 9.1 EPSS 58.9%

    When running Apache Cassandra with the following configuration: enable_user_defined_functions: true enable_scripted_user_defined_functions: true enable_user_defined_functions_threads: false it is possible for an attacker to execute arbitrary code on the host. The attacker would n...

  3. HighCVSS 7.5 EPSS 2.0%

    Apache Cassandra versions 2.1.0 to 2.1.22, 2.2.0 to 2.2.19, 3.0.0 to 3.0.23, and 3.11.0 to 3.11.9, when using 'dc' or 'rack' internode_encryption setting, allows both encrypted and unencrypted internode connections. A misconfigured node or a malicious user can use the unencrypted...

  4. MediumCVSS 5.9 EPSS 3.0%

    In Apache Cassandra, all versions prior to 2.1.22, 2.2.18, 3.0.22, 3.11.8 and 4.0-beta2, 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...

  5. CriticalCVSS 9.8 EPSS 2.3%

    The default configuration in Apache Cassandra 3.8 through 3.11.1 binds an unauthenticated JMX/RMI interface to all network interfaces, which allows remote attackers to execute arbitrary Java code via an RMI request. This issue is a regression of CVE-2015-0225. The regression was...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.