CVE-2020-17516

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

2.0% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2021-02-03 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:59 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.0% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2021-02-03 17:15 UTC

Last modified

2026-06-17 02:59 UTC

Exploit probability

2.0% · EPSS, next 30 days

Weakness

CWE-290

Record status

Modified

Affected

• Apache Cassandra ≤ 2.1.22
• Apache Cassandra ≤ 2.2.19
• Apache Cassandra ≤ 3.0.23
• Apache Cassandra ≤ 3.11.9

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-17516.md and follow it. Check whether this project is affected by CVE-2020-17516. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge