Root-volume disclosure via unvalidated PersistentVolume handles
Published Mar 7, 2024 · Updated Nov 14, 2025
Trust boundary violation in Red Hat OpenShift Container Platform 4.13 through 4.15 allows remote authenticated users to read worker-node root volumes. kubevirt-csi accepts an attacker-controlled volumeHandle and maps its predictable node-name-rhcos value to an infrastructure PVC without tenant-label or prefix validation. The attacker must be able to create PersistentVolumes in an HCP guest cluster; a crafted volume can then expose the selected node volume inside a pod.
Summary
What happened
Trust boundary violation in Red Hat OpenShift Container Platform 4.13 through 4.15 allows remote authenticated users to read worker-node root volumes. kubevirt-csi accepts an attacker-controlled volumeHandle and maps its predictable node-name-rhcos value to an infrastructure PVC without tenant-label or prefix validation. The attacker must be able to create PersistentVolumes in an HCP guest cluster; a crafted volume can then expose the selected node volume inside a pod.
The record
- CVE
- CVE-2024-1725
- Published
- Mar 7, 2024
- Updated
- Nov 14, 2025
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform 4.14
- Classifications
- CWE-501, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo