# CVE-2019-10175: Missing authorization in containerized-data-importer

> Attackers can clone any Persistent Volume Claim in the cluster to their namespace, accessing other users' data due to missing permission checks.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x7rm-228h-8xh9

## What is CVE-2019-10175?

CVE-2019-10175 is a medium-severity missing authorization vulnerability in KubeVirt containerized-data-importer, published on 28 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-10175?

It affects 1 product.


Products: Kubevirt Containerized-Data-Importer.

## How do I fix CVE-2019-10175?

No fix has been published for CVE-2019-10175 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-10175 being exploited?

There is no known exploitation of CVE-2019-10175 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10175 and fix it if it is affected.

What it is: CVE-2019-10175 is a medium-severity missing authorization vulnerability in KubeVirt containerized-data-importer, published on 28 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10175 in the wild and no public exploit code.

Affected product: KubeVirt containerized-data-importer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10175/ (Markdown: https://insights.sbomify.com/CVE-2019-10175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10175
- OSV: https://osv.dev/vulnerability/CVE-2019-10175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10175/
Summaries are generated and may contain mistakes; the official description above is the record.