dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2024-1725

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in the kubevirt-csi component of OpenShift Virtualization's Hosted Control Plane allows authenticated attackers to access the root HCP worker node's volume by creating a custom Persistent Volume with the same name as a worker node.

MitigationRestrict Persistent Volume creation permissions through RBAC policies and limit who can interact with the kubevirt-csi driver to prevent attackers from mounting worker node volumes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.13= 4.14= 4.15
Openshift Container Platform For Arm64Application
Affected:= 4.13= 4.14= 4.15
Openshift Container Platform For Ibm ZApplication
Affected:= 4.13= 4.14= 4.15
Openshift Container Platform For LinuxoneApplication
Affected:= 4.13= 4.14= 4.15
Openshift Container Platform For PowerApplication
Affected:= 4.13= 4.14= 4.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if OpenShift Virtualization Hosted Control Plane is deployed
    Run 'oc get hvms -A' to list Hyperconverged resources, or check for 'kubevirt-csi' namespace with 'oc get ns | grep kubevirt'
    Affected if kubevirt-csi namespace or Hyperconverged resources exist, indicating the vulnerable component is present
  2. Check kubevirt-csi operator installation status
    Run 'oc get deployment -n kubevirt-csi' and look for csi-driver-kubevirt-controller deployment, or query operator subscriptions with 'oc get subs -n openshift-csi'
    Affected if The csi-driver-kubevevirt-controller deployment exists and is running
  3. Enumerate Persistent Volumes in the cluster
    Run 'oc get pv -o jsonpath='{.items[*].metadata.name}'' to list all Persistent Volume names
    Affected if Any PV exists with a name matching an HCP worker node name (check worker node names with 'oc get nodes -l node-role.kubernetes.io/worker=')
  4. Check for kubevirt-csi StorageClass usage
    Run 'oc get storageclass | grep kubevirt' to identify kubevirt-csi StorageClasses, then check PVs using that StorageClass with 'oc get pv -o jsonpath="{.items[?(@.spec.storageClassName=~'kubevirt.*')].metadata.name}"'
    Affected if PVs are bound to kubevirt-csi StorageClasses and could potentially access node volumes
  5. Review RBAC permissions for Persistent Volume creation
    Run 'oc auth can-i create persistentvolumes --as=<system:serviceaccount>' for various users/groups, or inspect ClusterRoleBindings with 'oc get clusterrolebinding | grep -i persistentvolume'
    Affected if Users other than cluster-admins have permissions to create Persistent Volumes

If OpenShift Virtualization HCP with kubevirt-csi is deployed and non-admin users can create Persistent Volumes that match worker node names, the environment is vulnerable to CVE-2024-1725

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict Persistent Volume creation permissions through RBAC policies and limit who can interact with the kubevirt-csi driver to prevent attackers from mounting worker node volumes.

Recommended fix Moderate confidence

Consult Red Hat Security Advisory for specific fixed version (typically 4.16 or later patch release)

  1. Contact Red Hat customer support or consult the official Red Hat Security Advisory (RHSA) for CVE-2024-1725 to obtain the exact patch version and detailed remediation steps.
  2. Verify your OpenShift Container Platform version using 'oc get clusterversion'
  3. If running an affected version (4.13, 4.14, or 4.15), plan an upgrade to the version specified in the Red Hat Security Advisory as containing the fix.
  4. Before upgrading in production, test the upgrade in a staging environment to ensure compatibility with your workloads.
  5. After upgrading, verify the kubevirt-csi component has been updated and the vulnerability is remediated.
Caveat Review Red Hat upgrade documentation for any known compatibility issues between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1725 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data