Security readout for executives and security teams
Kubernetes control planes running affected kube-controller-manager versions can be abused by certain authenticated users to read a small amount of data from internal services reachable from the master host network. The issue is limited but sensitive because link-local or loopback services may expose credentials, metadata, or operational data. Exposure is most relevant to clusters running old Kubernetes control planes where users have the specific authorization needed to reach the vulnerable controller behavior. Public internet exposure is not required; insider, compromised account, or over-broad RBAC access is the concern. Treat this as a controlled but real confidentiality risk in legacy Kubernetes environments. It is not marked as actively exploited in the supplied sources, but affected control planes should be upgraded because internal endpoint leakage can expose sensitive operational data. Mitigation focus: Upgrade affected clusters to fixed Kubernetes releases or later vendor-supported versions.; Prioritize unsupported v1.0-v1.14 clusters for migration to a supported fixed release.; Review Kubernetes vendor and distribution advisories before applying platform-specific packages..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-8555 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N1.84Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://groups.google.com/d/topic/kubernetes-security-announce/kEK27tqqs30/discussionCVE reference · mailing-list, x_refsource_MLIST
- https://github.com/kubernetes/kubernetes/issues/91542CVE reference · x_refsource_CONFIRM
- FEDORA-2020-aeea04cd13CVE reference · vendor-advisory, x_refsource_FEDORA
- https://security.netapp.com/advisory/ntap-20200724-0005/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.