Skip to main content
No exploitation reportedFix available

CVE-2020-17516

No exploitation reported by the sources we read.

  • Published2021-02-03
  • Fixed in3.11.10 · 3.0.24 · 2.2.20 · 2.1.23
  • WeaknessCWE-290

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

dates in UTC
  1. 2021-02-0317:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-17516?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-17516?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD
cassandra
BranchAffectedFixed in
3.11≥ 3.11.0, < 3.11.103.11.10
3.0≥ 3.0.0, < 3.0.243.0.24
2.2≥ 2.2.0, < 2.2.202.2.20
2.1≥ 2.1.0, < 2.1.232.1.23
Apache cassandra
BranchAffectedFixed in
2.1≥ 2.1.0, ≤ 2.1.22no fix published
2.2≥ 2.2.0, ≤ 2.2.19no fix published
3.0≥ 3.0.0, ≤ 3.0.23no fix published
3.11≥ 3.11.0, ≤ 3.11.9no fix published
cassandra-all
BranchAffectedFixed in
3.11≥ 3.11.0, < 3.11.103.11.10
3.0≥ 2.1.0, < 3.0.243.0.24

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update cassandra to 3.11.10 · 3.0.24 · 2.2.20 · 2.1.23

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.5read 2026-10-23
  • NVDCVSS 2.04.3read 2026-10-23
  • CNAweakness (CWE)CWE-290read 2026-10-23
  • NVDweakness (CWE)CWE-290read 2026-10-23
  • FIRST EPSSEPSS score1.9 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2021-02-03
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-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_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.

Is CVE-2020-17516 actively exploited?

Active exploitation of CVE-2020-17516 has not been confirmed. Its EPSS score was 1.9% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-17516?

CVE-2020-17516 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running cassandra? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month