# CVE-2020-8555: Kubernetes kube-controller-manager SSRF > Authorized users can exploit SSRF in kube-controller-manager to leak sensitive information from internal host network endpoints. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`) - **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:** 4 Jun 2020 - **Updated:** 16 Sep 2024 - **Also known as:** CLEANSTART-2025-QE77299, DEBIAN-CVE-2020-8555, GHSA-x6mj-w4jf-jmgw, GO-2022-0890, RHSA-2020:2440, RHSA-2020:2448, RHSA-2020:2594 ## What is CVE-2020-8555? CVE-2020-8555 is a medium-severity server-side request forgery vulnerability in Fedoraproject Fedora, published on 4 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description The Kubernetes kube-controller-manager in versions v1.0-1.14, versions prior to v1.15.12, v1.16.9, v1.17.5, and version v1.18.0 are vulnerable to a Server Side Request Forgery (SSRF) that allows certain authorized users to leak up to 500 bytes of arbitrary information from unprotected endpoints within the master's host network (such as link-local or loopback services). Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2020-8555? 9 open source packages ship an affected version, including k8s.io/kubernetes. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `k8s.io/kubernetes` | Go | All versions | 1.15.12, 1.16.9, 1.17.4, 1.18.1 | | `k8s.io/kubernetes` | Go | All versions | 1.15.12 | | `k8s.io/kubernetes` | Go | All versions | 1.15.12 | | `k8s.io/kubernetes` | Go | From 1.16.0 | 1.16.9 | | `k8s.io/kubernetes` | Go | From 1.16.0 | 1.16.9 | | `k8s.io/kubernetes` | Go | From 1.17.0 | 1.17.4 | | `k8s.io/kubernetes` | Go | From 1.17.0 | 1.17.4 | | `k8s.io/kubernetes` | Go | From 1.18.0 | 1.18.1 | | `k8s.io/kubernetes` | Go | From 1.18.0 | 1.18.1 | | `openshift` | Red Hat:openshift:4.2::el7 | All versions | 0:4.2.36-202006211650.p0.git.0.1fe246f.el7 | | `openshift-hyperkube` | Red Hat:openshift:4.2::el7 | All versions | 0:4.2.36-202006211650.p0.git.0.1fe246f.el7 | | `openshift` | Red Hat:openshift:4.2::el8 | All versions | 0:4.2.36-202006211650.p0.git.0.1fe246f.el8 | | `openshift-hyperkube` | Red Hat:openshift:4.2::el8 | All versions | 0:4.2.36-202006211650.p0.git.0.1fe246f.el8 | | `openshift` | Red Hat:openshift:4.3::el7 | All versions | 0:4.3.25-202006060952.git.1.96c30f6.el7 | | `openshift-hyperkube` | Red Hat:openshift:4.3::el7 | All versions | 0:4.3.25-202006060952.git.1.96c30f6.el7 | | `openshift` | Red Hat:openshift:4.3::el8 | All versions | 0:4.3.25-202006060952.git.1.96c30f6.el8 | | `openshift-hyperkube` | Red Hat:openshift:4.3::el8 | All versions | 0:4.3.25-202006060952.git.1.96c30f6.el8 | | `openshift` | Red Hat:openshift:4.4::el7 | All versions | 0:4.4.0-202006061254.git.1.dc84fb4.el7 | | `openshift-hyperkube` | Red Hat:openshift:4.4::el7 | All versions | 0:4.4.0-202006061254.git.1.dc84fb4.el7 | | `openshift` | Red Hat:openshift:4.4::el8 | All versions | 0:4.4.0-202006061254.git.1.dc84fb4.el8 | | `openshift-hyperkube` | Red Hat:openshift:4.4::el8 | All versions | 0:4.4.0-202006061254.git.1.dc84fb4.el8 | Products: Fedoraproject Fedora, Kubernetes Kubernetes. ## How do I fix CVE-2020-8555? Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.15.12, 1.16.9, 1.17.4 or 1.18.1. ## Is CVE-2020-8555 being exploited? There is no known exploitation of CVE-2020-8555 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-8555 and fix it if it is affected. What it is: CVE-2020-8555 is a medium-severity server-side request forgery vulnerability in Fedoraproject Fedora, published on 4 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-8555 in the wild and no public exploit code. Affected packages and fixed versions: - k8s.io/kubernetes (Go): affected all versions; fixed in 1.15.12, 1.16.9, 1.17.4, 1.18.1 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.15.12 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.15.12 - k8s.io/kubernetes (Go): affected from 1.16.0; fixed in 1.16.9 - k8s.io/kubernetes (Go): affected from 1.16.0; fixed in 1.16.9 - k8s.io/kubernetes (Go): affected from 1.17.0; fixed in 1.17.4 - k8s.io/kubernetes (Go): affected from 1.17.0; fixed in 1.17.4 - k8s.io/kubernetes (Go): affected from 1.18.0; fixed in 1.18.1 - k8s.io/kubernetes (Go): affected from 1.18.0; fixed in 1.18.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-8555/ (Markdown: https://insights.sbomify.com/CVE-2020-8555/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8555 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8555 - OSV: https://osv.dev/vulnerability/CVE-2020-8555 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-8555/ Summaries are generated and may contain mistakes; the official description above is the record.