CVE-2020-8562

Bypass of Kubernetes API Server proxy TOCTOU

LOW
3.1
CVSS Score
Published: February 1, 2022 at 10:33 AM UTC
Updated: June 17, 2026 at 03:26 AM UTC
1 product affected across 1 vendorKubernetes

Using Kubernetes by Kubernetes?

Get instant alerts when new vulnerabilities affect Kubernetes - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.1
Exploit prediction
EPSS 1%

Description

As mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections from accessing link-local or localhost networks when making user-driven connections to Services, Pods, Nodes, or StorageClass service providers. As part of this mitigation Kubernetes does a DNS name resolution check and validates that response IPs are not in the link-local (169.254.0.0/16) or localhost (127.0.0.0/8) range. Kubernetes then performs a second DNS resolution without validation for the actual connection. If a non-standard DNS server returns different non-cached responses, a user may be able to bypass the proxy IP restriction and access private networks on the control plane.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 1.18.181.19.0 ≤ v ≤ 1.19.101.20.0 ≤ v ≤ 1.20.61.21.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-367

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card