[
https://issues.apache.org/jira/browse/CASSANDRA-16455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16455:
-------------------------------------------
Resolution: Fixed
Status: Resolved (was: Open)
2.2 is EOL, since the 4.0.0 release.
> 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
> Components: Local/Other
> Reporter: Mark Denihan
> Priority: Normal
> Fix For: 2.2.20
>
>
> 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-3b505a626...@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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
