CVE-2020-17516GHSA-2VXM-VP4C-FJFWBIT-CASSANDRA-2020-17516
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_encry
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.0.24, 3.11.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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 connection despite not being in the same rack or dc, and bypass mutual TLS requirement.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a Apache Cassandra
2.1.0 to 2.1.22, 2.2.0 to 2.2.19, 3.0.0 to 3.0.23, 3.11.0 to 3.11.9
- org.apache.cassandra:cassandra-allMaven
From 2.1.0 · fixed in 3.0.24
- org.apache.cassandra:cassandra-allMaven
From 3.11.0 · fixed in 3.11.10
References 5
mail-archives.apache.org
lists.apache.org
- thread.html/rd84bec24907617bdb72f7ec907cd7437a0fd5a8886eb55aa84dd1eb8@<commits.cassandra.apache.org>
- thread.html/rcb16f36cafa184dd159e94033f87d0fc274c4752d467f3a09f2ceae4@<commits.cassandra.apache.org>
- thread.html/r81243a412a37a22211754936a13856af07cc68a93d728c52807486e9@<commits.cassandra.apache.org>