Overview 39 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 6 public PoC · 3 EPSS ≥ 0.5
39matches
0in Waratek scope0.0%
0protected0.0%
1exploited2.6%
0CISA KEV0.0%
6public PoC15.4%
3EPSS ≥ 0.57.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
1
2.6%
Not applicable
38
97.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
39
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 15 / year
20161
Not applicable1
High1
not blocked1
No public exploit1
20170
20184
Not applicable4
High4
not blocked4
No public exploit4
20197
Outside Waratek scope1
Not applicable6
High7
not blocked7
Exploited1
Working exploit published2
No public exploit4
20201
Not applicable1
High1
not blocked1
Proof of concept only1
20212
Not applicable2
High2
not blocked2
Proof of concept only1
No public exploit1
20226
Not applicable6
High6
not blocked6
Proof of concept only2
No public exploit4
202315
Not applicable15
High15
not blocked15
Proof of concept only2
Forecast only1
No public exploit12
20241
Not applicable1
High1
not blocked1
No public exploit1
20250
20262
Not applicable2
High2
not blocked2
Proof of concept only1
No public exploit1
20162017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-4342 | High | 2026-03-19 | Not applicable | No public exploit | A security issue was discovered in ingress-nginx where a combination of Ingress annotations can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.) |
| CVE-2026-3288 | High | 2026-03-09 | Not applicable | Proof of concept only | A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/rewrite-target` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.) |
| CVE-2024-5154 | High | 2024-06-12 | Not applicable | No public exploit | A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system. |
| CVE-2023-5528 | High | 2023-11-14 | Not applicable | Proof of concept only | 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. |
| CVE-2023-3893 | High | 2023-11-03 | Not applicable | No public exploit | A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes running kubernetes-csi-proxy may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes running kubernetes-csi-proxy. |
| CVE-2022-3172 | High | 2023-11-03 | Not applicable | No public exploit | A security issue was discovered in kube-apiserver that allows an aggregated API server to redirect client traffic to any URL. This could lead to the client performing unexpected actions as well as forwarding the client's API server credentials to third parties. |
| CVE-2023-3955 | High | 2023-10-31 | Not applicable | No public exploit | 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. |
| CVE-2023-3676 | High | 2023-10-31 | Not applicable | Proof of concept only | 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. |
| CVE-2023-5044 | High | 2023-10-25 | Not applicable | Forecast only | Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation. |
| CVE-2023-5043 | High | 2023-10-25 | Not applicable | No public exploit | Ingress nginx annotation injection causes arbitrary command execution. |
| CVE-2022-4886 | High | 2023-10-25 | Not applicable | No public exploit | Ingress-nginx `path` sanitization can be bypassed with `log_format` directive. |
| CVE-2023-1943 | High | 2023-10-12 | Not applicable | No public exploit | Privilege Escalation in kOps using GCE/GCP Provider in Gossip Mode. |
| CVE-2022-4318 | High | 2023-09-25 | Not applicable | No public exploit | A vulnerability was found in cri-o. This issue allows the addition of arbitrary lines into /etc/passwd by use of a specially crafted environment variable. |
| CVE-2023-1260 | High | 2023-09-24 | Not applicable | No public exploit | An authentication bypass vulnerability was discovered in kube-apiserver. This issue could allow a remote, authenticated attacker who has been given permissions "update, patch" the "pods/ephemeralcontainers" subresource beyond what the default is. They would then need to create a new pod or patch one that they already have access to. This might allow evasion of SCC admission restrictions, thereby gaining control of a privileged pod. |
| CVE-2023-1944 | High | 2023-05-24 | Not applicable | No public exploit | This vulnerability enables ssh access to minikube container using a default password. |
| CVE-2021-25749 | High | 2023-05-24 | Not applicable | No public exploit | Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option to true. |
| CVE-2021-25748 | High | 2023-05-24 | Not applicable | No public exploit | A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use a newline character to bypass the sanitization of the `spec.rules[].http.paths[].path` field of an Ingress object (in the `networking.k8s.io` or `extensions` API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster. |
| CVE-2022-3294 | High | 2023-03-01 | Not applicable | No public exploit | Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network. |
| CVE-2022-2995 | High | 2022-09-19 | Not applicable | Proof of concept only | Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container. |
| CVE-2022-2385 | High | 2022-07-12 | Not applicable | No public exploit | A security issue was discovered in aws-iam-authenticator where an allow-listed IAM identity may be able to modify their username and escalate privileges. |
| CVE-2022-1708 | High | 2022-06-07 | Not applicable | No public exploit | A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after command execution, and it is read in a manner where the entire file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability. |
| CVE-2021-25746 | High | 2022-05-06 | Not applicable | No public exploit | A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use .metadata.annotations in an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster. |
| CVE-2021-25745 | High | 2022-05-06 | Not applicable | No public exploit | A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the spec.rules[].http.paths[].path field of an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster. |
| CVE-2022-0811 | High | 2022-03-16 | Not applicable | Proof of concept only | A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed. |
| CVE-2021-25742 | High | 2021-10-29 | Not applicable | No public exploit | A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the custom snippets feature to obtain all secrets in the cluster. |
| CVE-2021-25741 | High | 2021-09-20 | Not applicable | Proof of concept only | A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem. |
| CVE-2020-8558 | High | 2020-07-27 | Not applicable | Proof of concept only | The Kubelet and kube-proxy components in versions 1.1.0-1.16.10, 1.17.0-1.17.6, and 1.18.0-1.18.3 were found to contain a security issue which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. Such a service is generally thought to be reachable only by other processes on the same host, but due to this defeect, could be reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service. |
| CVE-2019-11253 | High | 2019-10-17 | Not applicable | Working exploit published | 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. |
| CVE-2019-11248 | High | 2019-08-29 | Not applicable | Exploited | The debugging endpoint /debug/pprof is exposed over the unauthenticated Kubelet healthz port. The go pprof endpoint is exposed over the Kubelet's healthz port. This debugging endpoint can potentially leak sensitive information such as internal Kubelet memory addresses and configuration, or for limited denial of service. Versions prior to 1.15.0, 1.14.4, 1.13.8, and 1.12.10 are affected. The issue is of medium severity, but not exposed by the default configuration. |
| CVE-2019-11247 | High | 2019-08-29 | Not applicable | No public exploit | The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12. |
| CVE-2019-11245 | High | 2019-08-29 | Not applicable | No public exploit | 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. |
| CVE-2019-11243 | High | 2019-04-22 | Not applicable | No public exploit | In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the affected versions, rest.AnonymousClientConfig() did not effectively clear service account credentials loaded using rest.InClusterConfig() |
| CVE-2019-9946 | High | 2019-04-02 | Outside Waratek scope | No public exploit | Cloud Native Computing Foundation (CNCF) CNI (Container Networking Interface) 0.7.4 has a network firewall misconfiguration which affects Kubernetes. The CNI 'portmap' plugin, used to setup HostPorts for CNI, inserts rules at the front of the iptables nat chains; which take precedence over the KUBE- SERVICES chain. Because of this, the HostPort/portmap rule could match incoming traffic even if there were better fitting, more specific service definition rules like NodePorts later in the chain. The issue is fixed in CNI 0.7.5 and Kubernetes 1.11.9, 1.12.7, 1.13.5, and 1.14.0. |
| CVE-2018-18264 | High | 2019-01-03 | Not applicable | Working exploit published | Kubernetes Dashboard before 1.10.1 allows attackers to bypass authentication and use Dashboard's Service Account for reading secrets within the cluster. |
| CVE-2018-1002103 | High | 2018-12-05 | Not applicable | No public exploit | In Minikube versions 0.3.0-0.29.0, minikube exposes the Kubernetes Dashboard listening on the VM IP at port 30000. In VM environments where the IP is easy to predict, the attacker can use DNS rebinding to indirectly make requests to the Kubernetes Dashboard, create a new Kubernetes Deployment running arbitrary code. If minikube mount is in use, the attacker could also directly access the host filesystem. |
| CVE-2016-7075 | High | 2018-09-10 | Not applicable | No public exploit | It was found that Kubernetes as used by Openshift Enterprise 3 did not correctly validate X.509 client intermediate certificate host name fields. An attacker could use this flaw to bypass authentication requirements by using a specially crafted X.509 certificate. |
| CVE-2018-1000400 | High | 2018-05-18 | Not applicable | No public exploit | Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9. |
| CVE-2017-1002102 | High | 2018-03-13 | Not applicable | No public exploit | In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using a secret, configMap, projected or downwardAPI volume can trigger deletion of arbitrary files/directories from the nodes where they are running. |
| CVE-2016-1905 | High | 2016-02-03 | Not applicable | No public exploit | The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object. |