A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.
This issue lets a highly privileged Kubernetes actor abuse admission webhook redirects so kube-apiserver reaches private network locations. The main business risk is limited information disclosure if that actor can also read verbose kube-apiserver logs. It is not listed as KEV and the provided sources do not show active exploitation.
Executive priority
Treat this as a moderate Kubernetes control-plane governance issue. Prioritize environments with shared cluster administration, third-party admission webhooks, or broad log access. It should not outrank actively exploited or unauthenticated vulnerabilities unless your cluster RBAC and logging practices match the described prerequisites.
Technical view
CVE-2020-8561 affects Kubernetes kube-apiserver handling of MutatingWebhookConfiguration or ValidatingWebhookConfiguration responses. A party controlling webhook responses can redirect apiserver requests to private networks reachable by the apiserver. If they can view kube-apiserver logs at level 10, redirected response headers and bodies may be exposed in logs.
Likely exposure
Exposure is most likely in Kubernetes environments where users or components can control admission webhook behavior and also access highly verbose kube-apiserver logs. The CVSS vector indicates high privileges are required, with low confidentiality impact and no integrity or availability impact identified in the bundle.
Exploitation context
The provided bundle supports a constrained abuse scenario, not broad unauthenticated exploitation. It requires control over webhook responses and access to kube-apiserver logs at log level 10. KEV is false, and no cited source in the bundle states active exploitation.
Researcher notes
The source bundle does not identify a specific fixed version or confirmed exploit activity. Analysis should focus on the admission webhook redirect behavior, privilege requirements, log-level dependency, and whether Kubernetes considers the CVE unresolved or reconciled in later guidance.
Mitigation direction
Restrict who can create or modify admission webhook configurations.
Restrict access to kube-apiserver logs, especially highly verbose logs.
Avoid kube-apiserver log level 10 in production unless operationally necessary.
Audit webhook configurations for unexpected redirect-capable endpoints or owners.
Check Kubernetes security guidance and issue 104720 for current vendor direction.
Validation and detection
Inventory clusters using MutatingWebhookConfiguration or ValidatingWebhookConfiguration.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-441: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-441 · source CWE mapping
Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.