Advisory

GHSA-qh36-44jv-c8xj

Also known as: CVE-2020-8562

Summary

Potential proxy IP restriction bypass in Kubernetes

Details

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. All versions of Kubernetes are impacted, and there is no fix in place.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2022-02-02 00:01 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

k8s.io/kubernetes

Go · All systems

Affected

  • introduced 1.21.0, last affected 1.21.1 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

k8s.io/kubernetes

Go · All systems

Affected

  • introduced 1.20.0, last affected 1.20.7 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

k8s.io/kubernetes

Go · All systems

Affected

  • introduced 1.19.0, last affected 1.19.11 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

k8s.io/kubernetes

Go · All systems

Affected

  • introduced 0, last affected 1.18.19 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences