p PatchFirst

PatchFirst · Latest vulnerabilities

kubernetes 1.27.16: known vulnerabilities

Known vulnerabilities affecting kubernetes 1.27.16: 5. Compare the fixes below with your installed release.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 5

  1. CVE-2020-8562

    Low · CVSS 2.2EPSS 1.08%No fix published

    Bypass of Kubernetes API Server proxy TOCTOU

    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

    Published Updated
  2. CVE-2020-8561

    Medium · CVSS 4.1EPSS 2.1%No fix published

    Webhook redirect in kube-apiserver

    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.

    Published Updated
  3. CVE-2020-8554

    Medium · CVSS 6.3EPSS 9.27%Public exploitNo fix published

    Kubernetes man in the middle using LoadBalancer or ExternalIPs

    Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect.

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →