p PatchFirst

PatchFirst · Vulnérabilités récentes

kubernetes 1.28.0 : vulnérabilités connues

Vulnérabilités connues concernant kubernetes 1.28.0 : 9. Comparez les versions corrigées ci-dessous avec celle que vous utilisez.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 9

  1. CVE-2024-10220

    Élevée · CVSS 8.1EPSS 3,03%Correctif disponible

    Arbitrary command execution through gitRepo volume

    The Kubernetes kubelet component allows arbitrary command execution via specially crafted gitRepo volumes.This issue affects kubelet: through 1.28.11, from 1.29.0 through 1.29.6, from 1.30.0 through 1.30.2.

    • Mettez à jour vers 1.28.12
    Publication Mise à jour
  2. CVE-2024-5321

    Moyenne · CVSS 6.1EPSS 0,31%Correctif disponible

    Incorrect permissions on Windows containers logs

    A security issue was discovered in Kubernetes clusters with Windows nodes where BUILTIN\Users may be able to read container logs and NT AUTHORITY\Authenticated Users may be able to modify container logs.

    • Mettez à jour vers 1.28.12
    Publication Mise à jour
  3. CVE-2023-5528

    Élevée · CVSS 7.2EPSS 4,09%Aucun correctif publié

    Kubernetes - Windows nodes - Insufficient input sanitization in in-tree storage plugin leads to privilege escalation

    A security issue was discovered in Kubernetes where a user that can create pods and persistent volumes on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they are using an in-tree storage plugin for Windows nodes.

    Publication Mise à jour
  4. CVE-2023-3955

    Élevée · CVSS 8.8EPSS 4%Aucun correctif publié

    Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation

    A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.

    Publication Mise à jour
  5. CVE-2023-3676

    Élevée · CVSS 8.8EPSS 13,16%Aucun correctif publié

    Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation

    A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.

    Publication Mise à jour
  6. CVE-2020-8562

    Faible · CVSS 2.2EPSS 1,19%Aucun correctif publié

    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

    Publication Mise à jour
  7. CVE-2020-8561

    Moyenne · CVSS 4.1EPSS 2,1%Aucun correctif publié

    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.

    Publication Mise à jour
  8. CVE-2020-8554

    Moyenne · CVSS 6.3EPSS 8,72%Code d’exploitation publicAucun correctif publié

    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.

    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →