Show filters
21 Total Results
Displaying 11-20 of 21
Sort by:
Attacker Value
Unknown
CVE-2024-5154
Disclosure Date: June 12, 2024 (last updated December 21, 2024)
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.
0
Attacker Value
Unknown
CVE-2024-3727
Disclosure Date: May 14, 2024 (last updated January 20, 2025)
A flaw was found in the github.com/containers/image library. This flaw allows attackers to trigger unexpected authenticated registry accesses on behalf of a victim user, causing resource exhaustion, local path traversal, and other attacks.
0
Attacker Value
Unknown
CVE-2024-4369
Disclosure Date: May 01, 2024 (last updated June 19, 2024)
An information disclosure flaw was found in OpenShift's internal image registry operator. The AZURE_CLIENT_SECRET can be exposed through an environment variable defined in the pod definition, but is limited to Azure environments. An attacker controlling an account that has high enough permissions to obtain pod information from the openshift-image-registry namespace could use this obtained client secret to perform actions as the registry operator's Azure service account.
0
Attacker Value
Unknown
CVE-2024-3154
Disclosure Date: April 26, 2024 (last updated June 05, 2024)
A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.
0
Attacker Value
Unknown
CVE-2024-1139
Disclosure Date: April 25, 2024 (last updated May 16, 2024)
A credentials leak vulnerability was found in the cluster monitoring operator in OCP. This issue may allow a remote attacker who has basic login credentials to check the pod manifest to discover a repository pull secret.
0
Attacker Value
Unknown
CVE-2024-0874
Disclosure Date: April 25, 2024 (last updated September 11, 2024)
A flaw was found in coredns. This issue could lead to invalid cache entries returning due to incorrectly implemented caching.
0
Attacker Value
Unknown
CVE-2024-1394
Disclosure Date: March 21, 2024 (last updated August 21, 2024)
A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey and ctx. That function uses named return parameters to free pkey and ctx if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey and ctx will be nil inside the deferred function that should free them.
0
Attacker Value
Unknown
CVE-2024-1753
Disclosure Date: March 18, 2024 (last updated May 24, 2024)
A flaw was found in Buildah (and subsequently Podman Build) which allows containers to mount arbitrary locations on the host filesystem into build containers. A malicious Containerfile can use a dummy image with a symbolic link to the root filesystem as a mount source and cause the mount operation to mount the host root filesystem inside the RUN step. The commands inside the RUN step will then have read-write access to the host filesystem, allowing for full container escape at build time.
0
Attacker Value
Unknown
CVE-2024-1725
Disclosure Date: March 07, 2024 (last updated May 08, 2024)
A flaw was found in the kubevirt-csi component of OpenShift Virtualization's Hosted Control Plane (HCP). This issue could allow an authenticated attacker to gain access to the root HCP worker node's volume by creating a custom Persistent Volume that matches the name of a worker node.
0
Attacker Value
Unknown
CVE-2023-6476
Disclosure Date: January 09, 2024 (last updated April 25, 2024)
A flaw was found in CRI-O that involves an experimental annotation leading to a container being unconfined. This may allow a pod to specify and get any amount of memory/cpu, circumventing the kubernetes scheduler and potentially resulting in a denial of service in the node.
0