CVE-2019-11245: falha de média gravidade em Kubernetes
kubelet-started container uid changes to root after first restart or if image is already pulled to the node
Publicada em · Atualizada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
13Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 4.9epss 0.6%
In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit runAsUser attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified mustRunAsNonRoot: true, the kubelet will refuse to start the container as root. If the pod did not specify mustRunAsNonRoot: true, the kubelet will run the container as uid 0.
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Produtos afetados
Kubernetes · KubernetesCVEs relacionadas — Kubernetes
No mesmo produto, das mais perigosas para as menos.
CVE-2018-1002105CRITICALCVE-2018-1002105EPSS 87.0%CVE-2019-11248MEDIUMKubernetes kubelet exposes /debug/pprof info on healthz portEPSS 75.1%CVE-2019-11253HIGHKubernetes API Server JSON/YAML parsing vulnerable to resource exhaustion attackEPSS 25.9%CVE-2019-1002100MEDIUMCVE-2019-1002100EPSS 16.9%CVE-2017-1002101HIGHCVE-2017-1002101EPSS 13.3%CVE-2019-1002101MEDIUMkubectl cp path traversalEPSS 12.8%