# CVE-2020-13597: Calico nodes IPv6 traffic redirection from route advertisment > A compromised pod can redirect node IPv6 traffic to itself, enabling information disclosure and traffic interception in clusters with IPv6 enabled. - **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Jun 2020 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-pf59-j7c2-rh6x ## What is CVE-2020-13597? CVE-2020-13597 is a medium-severity vulnerability in Tigera Inc Calico, published on 3 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-201 (Insertion of Sensitive Information Into Sent Data) ## Which versions are affected by CVE-2020-13597? 14 open source packages ship an affected version, including github.com/projectcalico/calico. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/projectcalico/calico` | Go | All versions | 3.8.9 | | `github.com/projectcalico/calico` | Go | All versions | 3.8.9 | | `github.com/projectcalico/calico` | Go | From 3.10.0 | 3.10.4 | | `github.com/projectcalico/calico` | Go | From 3.10.0 | 3.10.4 | | `github.com/projectcalico/calico` | Go | From 3.11.0 | 3.11.3 | | `github.com/projectcalico/calico` | Go | From 3.11.0 | 3.11.3 | | `github.com/projectcalico/calico` | Go | From 3.12.0 | 3.12.2 | | `github.com/projectcalico/calico` | Go | From 3.12.0 | 3.12.2 | | `github.com/projectcalico/calico` | Go | From 3.13.0 | 3.13.4 | | `github.com/projectcalico/calico` | Go | From 3.13.0 | 3.13.4 | | `github.com/projectcalico/calico` | Go | From 3.14.0 | 3.14.1 | | `github.com/projectcalico/calico` | Go | From 3.14.0 | 3.14.1 | | `github.com/projectcalico/calico` | Go | From 3.9.0 | 3.9.6 | | `github.com/projectcalico/calico` | Go | From 3.9.0 | 3.9.6 | Products: Projectcalico Calico. ## How do I fix CVE-2020-13597? Upgrade github.com/projectcalico/calico to a fixed version for your release line: 3.8.9, 3.10.4, 3.11.3 or 3.12.2. ## Is CVE-2020-13597 being exploited? There is no known exploitation of CVE-2020-13597 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-13597 and fix it if it is affected. What it is: CVE-2020-13597 is a medium-severity vulnerability in Tigera Inc Calico, published on 3 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-13597 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/projectcalico/calico (Go): affected all versions; fixed in 3.8.9 - github.com/projectcalico/calico (Go): affected all versions; fixed in 3.8.9 - github.com/projectcalico/calico (Go): affected from 3.10.0; fixed in 3.10.4 - github.com/projectcalico/calico (Go): affected from 3.10.0; fixed in 3.10.4 - github.com/projectcalico/calico (Go): affected from 3.11.0; fixed in 3.11.3 - github.com/projectcalico/calico (Go): affected from 3.11.0; fixed in 3.11.3 - github.com/projectcalico/calico (Go): affected from 3.12.0; fixed in 3.12.2 - github.com/projectcalico/calico (Go): affected from 3.12.0; fixed in 3.12.2 - github.com/projectcalico/calico (Go): affected from 3.13.0; fixed in 3.13.4 - github.com/projectcalico/calico (Go): affected from 3.13.0; fixed in 3.13.4 - github.com/projectcalico/calico (Go): affected from 3.14.0; fixed in 3.14.1 - github.com/projectcalico/calico (Go): affected from 3.14.0; fixed in 3.14.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-13597/ (Markdown: https://insights.sbomify.com/CVE-2020-13597/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13597 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13597 - OSV: https://osv.dev/vulnerability/CVE-2020-13597 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-13597/ Summaries are generated and may contain mistakes; the official description above is the record.