# CVE-2017-1000199: Information disclosure in n/a

> Non-privileged users can check for the existence of any file with root privileges via the tcmu-runner qcow handler.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mm98-g27p-4qwj

## What is CVE-2017-1000199?

CVE-2017-1000199 is a high-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tcmu-runner version 0.91 up to 1.20 is vulnerable to information disclosure in handler_qcow.so resulting in non-privileged users being able to check for existence of any file with root privileges.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-1000199?

It affects 1 product.


Products: Tcmu-Runner Project Tcmu-Runner.

## How do I fix CVE-2017-1000199?

Apply the vendor's patch.

## Is CVE-2017-1000199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3139](https://insights.sbomify.com/CVE-2021-3139/): Path traversal in n/a (high 8.1)
- [CVE-2017-1000198](https://insights.sbomify.com/CVE-2017-1000198/): Denial of service in n/a (high 7.5)
- [CVE-2017-1000200](https://insights.sbomify.com/CVE-2017-1000200/): Null dereference in n/a (high 7.5)
- [CVE-2017-1000201](https://insights.sbomify.com/CVE-2017-1000201/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000199 and fix it if it is affected.

What it is: CVE-2017-1000199 is a high-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000199 in the wild and no public exploit code.

Affected product: n/a. 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-2017-1000199/ (Markdown: https://insights.sbomify.com/CVE-2017-1000199/index.md)
```

## Sources

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

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