Kubernetes 1.22.11

CPE Details

Kubernetes 1.22.11
kubernetes
kubernetes
1.22.11
2023-05-31
13h58 +00:00
2023-06-01
09h46 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:kubernetes:kubernetes:1.22.11:-:*:*:*:*:*:*

Informations

Vendor

kubernetes

Product

kubernetes

Version

1.22.11

Update

-

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-5528 2023-11-14 20h32 +00:00 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.
8.8
High
CVE-2023-3955 2023-10-31 20h36 +00:00 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.
8.8
High
CVE-2023-3676 2023-10-31 20h22 +00:00 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.
8.8
High
CVE-2023-2728 2023-07-03 20h06 +00:00 Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers.
6.5
Medium
CVE-2023-2727 2023-07-03 20h05 +00:00 Users may be able to launch containers using images that are restricted by ImagePolicyWebhook when using ephemeral containers. Kubernetes clusters are only affected if the ImagePolicyWebhook admission plugin is used together with ephemeral containers.
6.5
Medium
CVE-2023-2431 2023-06-16 07h08 +00:00 A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.
5.5
Medium
CVE-2021-25749 2023-05-23 22h00 +00:00 Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option to true.
7.8
High
CVE-2022-3162 2023-02-28 23h00 +00:00 Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.
6.5
Medium
CVE-2022-3294 2023-02-28 23h00 +00:00 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.
8.8
High
CVE-2020-8554 2021-01-21 17h09 +00:00 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.
6.3
Medium