Skip to content
Connect AISign inSign up free
CVE-2020-85622.2LowCWE-367

CVE-2020-8562: Bypass of Kubernetes API Server proxy TOCTOU

Kubernetes

Affected: Kubernetes · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.2%probability of exploitation in the next 30 days
68th percentile
050100

Higher than 68% of scored CVEs

2.2LowCVSS 3.1
Low

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Kubernetes · Kubernetes0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Published
February 2022

Disclosed bug bounty reports about CVE-2020-8562

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

CoverageNo articles yet

No CyberSIXT article names CVE-2020-8562 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References