dbcve.org
Containerized Data ImporterApplication · Kubevirt

CVE-2019-10175

MEDIUM · 6.5 CVSS v3.1 Published 2019-06-28
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 containerized-data-importer in virt-cdi-cloner, version 1.4, where the host-assisted cloning feature does not determine whether the requesting user has permission to access the Persistent Volume Claim (PVC) in the source namespace. This could allow users to clone any PVC in the cluster into their own namespace, effectively allowing access to other user's data.

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 · high confidence

The containerized-data-importer's virt-cdi-cloner in version 1.4 lacks authorization checks when performing host-assisted PVC cloning. The cloning function does not verify whether the requesting user has permission to access the source PVC in the source namespace, allowing any authenticated user to clone any PVC in the cluster into their own namespace.

MitigationImplement authorization checks in the cloning workflow to verify the requesting user has appropriate permissions (via RBAC) on the source PVC before allowing the clone operation to proceed.

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
Containerized Data ImporterApplication
Affected:= 1.4.0

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. Verify CDI version
    Run 'kubectl get cdiconfig' or check the containerized-data-importer deployment version to determine if version 1.4.0 is installed
    Affected if The installed CDI version equals exactly 1.4.0
  2. Confirm PVC cloning feature is in use
    Check for existing PVC clones in the cluster using 'kubectl get pvc -A' and look for any PVCs with data source references, or check CDI clonable DataVolumes with 'kubectl get datavolumes -A'
    Affected if Any PVC cloning or DataVolume cloning operations have been performed in the cluster
  3. Inspect RBAC for cloning permissions
    Review ClusterRole and Role bindings related to CDI cloning: check for 'cdi.cloner' verbs in ClusterRole bindings, and verify whether any authenticated users or service accounts have broad clone permissions without namespace restrictions
    Affected if Users or service accounts have clone permissions that are not restricted to source PVCs in their own namespace or lack proper source PVC access validation
  4. Check for unauthorized cross-namespace PVC access
    Audit existing PVC clones to identify any that clone from a different namespace than the target namespace, using 'kubectl get pvc -A -o jsonpath={.items[*].spec.dataSource}' to examine dataSource references
    Affected if PVC clones exist where the source PVC is in a different namespace than the clone target namespace and the user performing the clone should not have had access to the source PVC
  5. Verify cloning API endpoint accessibility
    Check if the CDI cloner API endpoint is accessible to unprivileged users: review API server logs for CDI clone requests or check if the 'cdi.cloner' clusterrole is bound to users outside the CDI operator namespace
    Affected if The CDI cloning API can be invoked by any authenticated user in the cluster without RBAC enforcement on the source PVC

A user is affected if Kubevirt CDI version 1.4.0 is running and PVC cloning functionality is enabled, as the authorization flaw allows any authenticated user to clone PVCs across namespaces without source permission verification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authorization checks in the cloning workflow to verify the requesting user has appropriate permissions (via RBAC) on the source PVC before allowing the clone operation to proceed.

Fix this in Containerized Data Importer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10175 — 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-2019-10175 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