...
The kube-hunter vulnerabilities listed as 'Yes' in the 'Critical' column MUST be resolved.
| Kube-Hunter Vulnerability | CVE | Critical | Remediation | |
| 1 | KHV002 - Kubernetes version disclosure | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 2 | KHV003 - Azure Metadata Exposure | No - Azure Only | ||
| 3 | KHV004 - Azure SPN Exposure | No - Azure Only | ||
| 4 | KHV005 - Access to Kubernetes API | Yes | ||
| 5 | KHV006 - Insecure (HTTP) access to Kubernetes API | Yes | Ensure your setup is exposing kube-api only on an HTTPS port. | |
| Do not enable kube-api’s --insecure-port flag in production. | ||||
| 6 | KHV007 - Specific Access to Kubernetes API | Yes | Review the RBAC permissions to Kubernetes API server for the anonymous and default service account. | |
| Depending on the Kubernetes cluster setup and preferences this may not be a problem. | ||||
| 7 | KHV020 - Possible Arp Spoof | Yes | Consider dropping the NET_RAW capability from your pods using Pod.spec.securityContext.capabilities | |
| 8 | KHV021 - Certificate Includes Email Address | Yes | Do not include email address in the Kubernetes API server certificate. (You should continue to use certificates to secure the API Server!) | |
| 9 | KHV022 - Critical Privilege Escalation CVE | CVE-2018-1002105 | Yes | Kubernetes v1.0.x-1.9.x – no fix available |
| Kubernetes v1.10.0-1.10.10 – fixed in v1.10.11 | ||||
| Kubernetes v1.11.0-1.11.4 – fixed in v1.11.5 | ||||
| Kubernetes v1.12.0-1.12.2 – fixed in v1.12.3 | ||||
| 10 | KHV023 - Denial of Service to Kubernetes API Server | CVE-2019-1002100 | Yes | Upgrade your kube-apiserver to newer versions, namely v1.11.8, v1.12.6, or v1.13.4 |
| If you cannot upgrade, or until you do, the best course of action is to remove patch permissions from untrusted users, or generally from admins who don’t really use it. | ||||
| 12 | KHV024 - Possible Ping Flood Attack | CVE-2019-9512 | Yes | Disable HTTP/2 support OR obtain a software patch if available |
| 13 | CVE-2019-9514 | Yes | Disable HTTP/2 support OR obtain a software patch if available | |
| 14 | KHV026 - Arbitrary Access To Cluster Scoped Resources | CVE-2019-11247 | Yes | Vulnerable versions: Fixed versions: |
| Kubernetes 1.7.x-1.12.x Fixed in v1.13.9 by #80852 | ||||
| Kubernetes 1.13.0-1.13.8 Fixed in v1.14.5 by #80851 | ||||
| Kubernetes 1.14.0-1.14.4 Fixed in v1.15.2 by #80850 | ||||
| Kubernetes 1.15.0-1.15.1 Fixed in master by #80750 | ||||
| 15 | KHV027 - Kubectl Vulnerable To CVE-2019-11246 | CVE-2019-11246 | Yes | Update your kubectl client to one of the following versions: 1.12.9, 1.13.6, 1.14.2 |
| 16 | KHV028 - Kubectl Vulnerable To CVE-2019-1002101 | CVE-2019-1002101 | Yes | The issue is resolved in kubectl v1.11.9, v1.12.7, v1.13.5, and v1.14.0. |
| 17 | KHV029 - Dashboard Exposed | Yes | Do not leave the Dashboard insecured. | |
| 18 | KHV030 - Possible DNS Spoof | Yes | Consider using DNS over TLS. CoreDNS (the common DNS server for Kubernetes) supports this out of the box, but your client applications might not. | |
| 19 | KHV031 - Etcd Remote Write Access Event | Yes | Ensure your etcd is accepting connections only from the Kubernetes API, using the --trusted-ca-file etcd flag. This is usually done by the installer, or cloud platform. | |
| 20 | KHV032 - Etcd Remote Read Access Event | Yes | Ensure your etcd is accepting connections only from the Kubernetes API, using the --trusted-ca-file etcd flag. This is usually done by the installer, or cloud platform. | |
| 21 | KHV033 - Etcd Remote version disclosure | Yes | ||
| 22 | KHV034 - Etcd is accessible using insecure connection (HTTP) | Yes | Ensure your setup is exposing etcd only on an HTTPS port by using the etcd flags --key-file and --cert-file. | |
| 23 | KHV036 - Anonymous Authentication | Yes | Ensure kubelet is protected using --anonymous-auth=false kubelet flag. Allow only legitimate users using --client-ca-file or --authentication-token-webhook kubelet flags. This is usually done by the installer or cloud provider. | |
| 24 | KHV037 - Exposed Container Logs | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 25 | KHV038 - Exposed Running Pods | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 26 | KHV039 - Exposed Exec On Container | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 27 | KHV040 - Exposed Run Inside Container | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 28 | KHV041 - Exposed Port Forward | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 29 | KHV042 - Exposed Attaching To Container | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 30 | KHV043 - Cluster Health Disclosure | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 31 | KHV044 - Privileged Container | Yes | Minimize the use of privileged containers. Use Pod Security Policies to enforce using privileged: false policy. | |
| 32 | KHV045 - Exposed System Logs | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 33 | KHV046 - Exposed Kubelet Cmdline | Yes | Disable --enable-debugging-handlers kubelet flag. | |
| 34 | KHV047 - Pod With Mount To /var/log | Yes | Consider disallowing running as root: Using Kubernetes Pod Security Policies with MustRunAsNonRoot policy. | |
| Consider disallowing writable host mounts to /var/log: Using Kubernetes Pod Security Policies with AllowedHostPaths policy. | ||||
| 35 | KHV049 - kubectl proxy Exposed | Ye | Expose your applications in a permanent, legitimate way, such as via Ingress. | |
| Close open proxies immediately after use. | ||||
| 36 | KHV050 - Read access to Pod service account token | Yes | It is recommended to explicitly specify a Service Account for all of your workloads (serviceAccountName in Pod.Spec), and manage their permissions according to the least privilege principle. | |
| Consider opting out automatic mounting of SA token using automountServiceAccountToken: false on ServiceAccount resource or Pod.spec. | ||||
| 37 | Access to pod's secrets | Yes | https://blog.aquasec.com/managing-kubernetes-secrets | |
| Securing etcd—secret data is stored in etcd. By default, etcd data is not encrypted and neither are your secrets. You should enable encryption at rest, limit access to etcd to admin users only, and safely dispose of disks where etcd data was formerly stored | ||||
| Use SSL/TLS—when running etcd in a cluster, you must use secure peer-to-peer communication. | ||||
| 38 | CAP_NET_RAW Enabled | Yes - If applicable | CAP_NET_RAW is used to open a raw socket and is used by ping. If this is not required CAP_NET_RAW MUST be removed. | |
| https://www.suse.com/c/demystifying-containers-part-iv-container-security/ |
Jira tickets tracking integration with Bluval:
...