# CVE-2016-6310: Information disclosure in n/a

> oVirt Engine logs the HTTPS PKI trust store password, allowing attackers with log access to read sensitive credentials.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qmxw-f8mx-gj65

## What is CVE-2016-6310?

CVE-2016-6310 is a medium-severity vulnerability in n/a, published on 22 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

oVirt Engine discloses the ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD in /var/log/ovirt-engine/engine.log file in RHEV before 4.0.

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

## Which versions are affected by CVE-2016-6310?

It affects 1 product.


Products: Redhat Enterprise Virtualization.

## How do I fix CVE-2016-6310?

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

## Is CVE-2016-6310 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5201](https://insights.sbomify.com/CVE-2015-5201/): Auth bypass in Enterprise Virtualization Hypervisor (aka RHEV-H) (high 7.5)
- [CVE-2013-2151](https://insights.sbomify.com/CVE-2013-2151/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2152](https://insights.sbomify.com/CVE-2013-2152/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2176](https://insights.sbomify.com/CVE-2013-2176/): Privilege escalation in n/a (high 7.2)
- [CVE-2017-2614](https://insights.sbomify.com/CVE-2017-2614/): Auth bypass in ovirt-engine-extension-aaa-jdbc (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6310 and fix it if it is affected.

What it is: CVE-2016-6310 is a medium-severity vulnerability in n/a, published on 22 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6310 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-2016-6310/ (Markdown: https://insights.sbomify.com/CVE-2016-6310/index.md)
```

## Sources

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

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