CVSS: 6.5EPSS: 0%CPEs: 4EXPL: 0CVE-2020-8551 – Kubernetes kubelet denial of service
https://notcve.org/view.php?id=CVE-2020-8551
The Kubelet component in versions 1.15.0-1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via the kubelet API, including the unauthenticated HTTP read-only API typically served on port 10255, and the authenticated HTTPS API typically served on port 10250. Se detectó que el componente Kubelet en versiones 1.15.0-1.15.9, versiones 1.16.0-1.16.6 y versiones 1.17.0-1.17.2, es vulnerable a un ataque de denegación de servicio por medio la API de kubelet, incluyendo la API de solo lectura HTTP no autenticada típicamente servida en el puerto 10255, y la API HTTPS autenticada típicamente servida en el puerto 10250. A denial of service flaw was found in Kubernetes' Kubelet API. A remote attacker can exploit this flaw by sending repeated, crafted HTTP requests to exhaust available memory and cause a crash. • https://github.com/kubernetes/kubernetes/issues/89377 https://groups.google.com/forum/#%21topic/kubernetes-security-announce/2UOlsba2g0s https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX https://security.netapp.com/advisory/ntap-20200413-0003 https://access.redhat.com/security/cve/CVE-2020-8551 https://bugzilla.redhat.com/show_bug.cgi?id=1816403 • CWE-400: Uncontrolled Resource Consumption CWE-770: Allocation of Resources Without Limits or Throttling CWE-789: Memory Allocation with Excessive Size Value •
CVSS: 5.7EPSS: 0%CPEs: 4EXPL: 0CVE-2019-11251 – kubectl cp allows symlink directory traversal
https://notcve.org/view.php?id=CVE-2019-11251
The Kubernetes kubectl cp command in versions 1.1-1.12, and versions prior to 1.13.11, 1.14.7, and 1.15.4 allows a combination of two symlinks provided by tar output of a malicious container to place a file outside of the destination directory specified in the kubectl cp invocation. This could be used to allow an attacker to place a nefarious file using a symlink, outside of the destination tree. El comando kubectl cp de Kubernetes en las versiones 1.1-1.12 y versiones anteriores a 1.13.11, 1.14.7 y 1.15.4, permite una combinación de dos enlaces simbólicos proporcionados mediante la salida tar de un contenedor malicioso para colocar un archivo fuera del directorio de destino especificado en la invocación de kubectl cp. Esto podría ser usado para permitir aun atacante colocar un archivo nefasto usando un enlace simbólico, fuera del árbol de destino. • https://github.com/kubernetes/kubernetes/issues/87773 https://groups.google.com/d/msg/kubernetes-announce/YYtEFdFimZ4/nZnOezZuBgAJ https://access.redhat.com/security/cve/CVE-2019-11251 https://bugzilla.redhat.com/show_bug.cgi?id=1753495 • CWE-59: Improper Link Resolution Before File Access ('Link Following') CWE-61: UNIX Symbolic Link (Symlink) Following •
CVSS: 7.5EPSS: 2%CPEs: 8EXPL: 1CVE-2019-11253 – Kubernetes API Server JSON/YAML parsing vulnerable to resource exhaustion attack
https://notcve.org/view.php?id=CVE-2019-11253
Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility. La comprobación de entrada inapropiada en el servidor API de Kubernetes en las versiones v1.0 hasta 1.12 y versiones anteriores a v1.13.12, v1.14.8, v1.15.5 y v1.16.2, permite a los usuarios autorizados enviar cargas maliciosas de YAML o JSON, causando que el servidor API consuma demasiada CPU o memoria, fallando potencialmente y dejando de estar disponible. En versiones anteriores a v1.14.0, la política predeterminada de RBAC autorizaba a los usuarios anónimos para enviar peticiones que pudieran desencadenar esta vulnerabilidad. • https://access.redhat.com/errata/RHSA-2019:3239 https://access.redhat.com/errata/RHSA-2019:3811 https://access.redhat.com/errata/RHSA-2019:3905 https://github.com/kubernetes/kubernetes/issues/83253 https://groups.google.com/forum/#%21topic/kubernetes-security-announce/jk8polzSUxs https://security.netapp.com/advisory/ntap-20191031-0006 https://access.redhat.com/security/cve/CVE-2019-11253 https://bugzilla.redhat.com/show_bug.cgi?id=1757701 • CWE-20: Improper Input Validation CWE-400: Uncontrolled Resource Consumption CWE-776: Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') •
CVSS: 6.5EPSS: 0%CPEs: 10EXPL: 0CVE-2019-11250 – Kubernetes client-go logs authorization headers at debug verbosity levels
https://notcve.org/view.php?id=CVE-2019-11250
The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected. La biblioteca de servicio de cliente de Kubernetes registra los encabezados de solicitud en niveles de detalle de 7 o superior. Esto puede revelar las credenciales a los usuarios no autorizados a través de los registros o la salida del comando. • http://www.openwall.com/lists/oss-security/2020/10/16/2 https://access.redhat.com/errata/RHSA-2019:4052 https://access.redhat.com/errata/RHSA-2019:4087 https://github.com/kubernetes/kubernetes/issues/81114 https://security.netapp.com/advisory/ntap-20190919-0003 https://access.redhat.com/security/cve/CVE-2019-11250 https://bugzilla.redhat.com/show_bug.cgi?id=1740434 • CWE-532: Insertion of Sensitive Information into Log File •