You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mark Denihan (Jira)" <ji...@apache.org> on 2021/02/17 15:50:00 UTC
[jira] [Created] (CASSANDRA-16455) CVE-2020-17516 mitigation in
2.2.x branch
Mark Denihan created CASSANDRA-16455:
----------------------------------------
Summary: CVE-2020-17516 mitigation in 2.2.x branch
Key: CASSANDRA-16455
URL: https://issues.apache.org/jira/browse/CASSANDRA-16455
Project: Cassandra
Issue Type: Bug
Reporter: Mark Denihan
As a Cassandra 2.2.x user
I would like to know if a fix is planned for CVE-2020-17516 in this branch
https://mail-archives.apache.org/mod_mbox/cassandra-user/202102.mbox/%3c6E4340A5-D7BE-4D33-9EC5-3B505A626D8D@apache.org%3e
{quote}CVE-2020-17516: Apache Cassandra doesn't enforce encryption setting on inbound internode connections
Severity:
Important
Vendor:
The Apache Software Foundation
Versions Affected:
Cassandra 2.1.0 to 2.1.22
Cassandra 2.2.0 to 2.2.19
Cassandra 3.0.0 to 3.0.23
Cassandra 3.11.0 to 3.11.9
....
....
....
Mitigation:
Users of ALL versions should switch from ‘dc’ or ‘rack’ to ‘all’ internode_encryption
setting, as they are inherently insecure
3.0.x users should additionally upgrade to 3.0.24
3.11.x users should additionally upgrade to 3.11.24
{quote}
I can't find any ticket tracking implementing this fix in 2.2.x or 2.1.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org