Is CVE-2020-8562 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-8562 being exploited in the wild.

How severe is CVE-2020-8562?

Low severity, with a CVSS score of 3.1, published 2 February 2022.

Which products and versions are affected?

k8s.io/kubernetes (Go) SEMVER:introduced=0, SEMVER:introduced=1.21.0,last_affected=1.21.1; Kubernetes <= 1.18.19, 1.19.0-1.19.11, 1.20.0-1.20.7, 1.21.0-1.21.1.

Is there a fix for CVE-2020-8562?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2020-8562 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2020-8562?

Check whether you run k8s.io/kubernetes (Go) or Kubernetes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-8562: Kubernetes proxy IP restriction bypass via DNS TOCTOU

Q: Is there a fix for CVE-2020-8562?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2020-8562 attacked?

It is attacked over the network, in an operating system.

Q: Am I affected by CVE-2020-8562?

Check whether you run k8s.io/kubernetes (Go) or Kubernetes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-8562 · Severity: low · CVSS 3.1 · Published 2022-02-02

Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. A vulnerability exists where the system's security checks can be bypassed, potentially allowing an attacker to access private internal networks on the control plane. This could lead to unauthorized access to sensitive internal services or data that should otherwise be restricted.

Technologies: k8s.io/kubernetes (Go), Kubernetes. Vendors: Go, Kubernetes.

Quick answers

Is CVE-2020-8562 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2020-8562 being exploited in the wild.
How severe is CVE-2020-8562?: Low severity, with a CVSS score of 3.1, published 2 February 2022.
Which products and versions are affected?: k8s.io/kubernetes (Go) SEMVER:introduced=0, SEMVER:introduced=1.21.0,last_affected=1.21.1; Kubernetes <= 1.18.19, 1.19.0-1.19.11, 1.20.0-1.20.7, 1.21.0-1.21.1.
Is there a fix for CVE-2020-8562?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2020-8562 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2020-8562?: Check whether you run k8s.io/kubernetes (Go) or Kubernetes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Time-of-Check Time-of-Use (TOCTOU) vulnerability exists in Kubernetes' proxy IP restriction logic. When making user-driven connections to Services, Pods, Nodes, or StorageClass providers, Kubernetes performs an initial DNS resolution to validate that the resulting IP is not in the link-local (169.254.0.0/16) or localhost (127.0.0.0/8) range. However, it then performs a second, unvalidated DNS resolution for the actual connection. An attacker using a malicious DNS server can return a safe IP for the first check and a restricted IP for the second, bypassing the mitigation. This requires network access and low privileges. At the time of advisory, no fix was available.

Affected products

Kubernetes Kubernetes <= 1.18.19, 1.19.0-1.19.11, 1.20.0-1.20.7, 1.21.0-1.21.1

Identifiers

CVE-2020-8562
GHSA-qh36-44jv-c8xj
GO-2022-0617

Timeline

2022-02-01: disclosed: NVD publication date
2022-02-02: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.