CVE-2020-13597GHSA-PF59-J7C2-RH6X
Calico nodes IPv6 traffic redirection from route advertisment
- 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.14.1, 3.13.4, 3.12.2, 3.11.3, 3.10.4, and 2 more
- 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
Clusters using Calico (version 3.14.0 and below), Calico Enterprise (version 2.8.2 and below), may be vulnerable to information disclosure if IPv6 is enabled but unused. A compromised pod with sufficient privilege is able to reconfigure the node’s IPv6 interface due to the node accepting route advertisement by default, allowing the attacker to redirect full or partial network traffic from the node to the compromised pod.
Timeline
- CVE published
- Record last updated
Affected versions
- Tigera Inc Calico
through 3.13.3; through 3.12.1; through 3.11.2; through 3.10.3; through 3.9.5; through 3.8.8
- Tigera Inc Calico Enterprise
through 2.8.2; through 2.7.4; through 2.6.2
- github.com/projectcalico/calicoGo
From 3.14.0 · fixed in 3.14.1
- github.com/projectcalico/calicoGo
From 3.13.0 · fixed in 3.13.4
- github.com/projectcalico/calicoGo
From 3.12.0 · fixed in 3.12.2
- github.com/projectcalico/calicoGo
From 3.11.0 · fixed in 3.11.3
- github.com/projectcalico/calicoGo
From 3.10.0 · fixed in 3.10.4
- github.com/projectcalico/calicoGo
From 3.9.0 · fixed in 3.9.6
- github.com/projectcalico/calicoGo
fixed in 3.8.9