CRI-O UnMountPodLogs/LinkContainerLogs emptyDirVolName path traversal

Summaryinfo

A vulnerability was found in CRI-O. It has been rated as critical. The impacted element is the function UnMountPodLogs/LinkContainerLogs. The manipulation of the argument emptyDirVolName leads to path traversal. This vulnerability is documented as CVE-2025-0750. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in CRI-O (version unknown) and classified as critical. This issue affects the function UnMountPodLogs/LinkContainerLogs. The manipulation of the argument emptyDirVolName with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A vulnerability was found in CRI-O. A path traversal issue in the log management functions (UnMountPodLogs and LinkContainerLogs) may allow an attacker with permissions to create and delete Pods to unmount arbitrary host paths, leading to node-level denial of service by unmounting critical system directories.

It is possible to read the advisory at bugzilla.redhat.com. The identification of this vulnerability is CVE-2025-0750. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 216062 (RHEL 8 / 9 : OpenShift Container Platform 4.17.16 (RHSA-2025:1122)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (216062). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• CRI-O

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion