# CVE-2016-8514: A remote information disclosure in HPE Version Control Repository Manager (VCRM) was found.


- **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
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fmx7-35m5-54mg

## What is CVE-2016-8514?

CVE-2016-8514 is a medium-severity vulnerability in Hewlett Packard Enterprise Version Control Repository Manager (VCRM), published on 15 Feb 2018. 

### Official description

A remote information disclosure in HPE Version Control Repository Manager (VCRM) was found. The problem impacts all versions prior to 7.6.

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

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

It affects 1 product.


Products: Hp Version Control Repository Manager.

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

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

## Is CVE-2016-8514 being exploited?

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

## Other vulnerabilities in Hewlett Packard Enterprise Version Control Repository Manager (VCRM)

- [CVE-2016-8515](https://insights.sbomify.com/CVE-2016-8515/): File upload in Version Control Repository Manager (VCRM) (high 8.8)
- [CVE-2016-8513](https://insights.sbomify.com/CVE-2016-8513/): Cross-site request forgery in Version Control Repository Manager (VCRM) (high 8.0)
- [CVE-2015-5409](https://insights.sbomify.com/CVE-2015-5409/): Memory corruption in n/a (high 7.5)
- [CVE-2015-5411](https://insights.sbomify.com/CVE-2015-5411/): Information disclosure in n/a (medium 6.8)
- [CVE-2017-5787](https://insights.sbomify.com/CVE-2017-5787/): Denial of service in Version Control Repository Manager (VCRM) (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8514 is a medium-severity vulnerability in Hewlett Packard Enterprise Version Control Repository Manager (VCRM), published on 15 Feb 2018. 
Exploitation: There is no known exploitation of CVE-2016-8514 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise Version Control Repository Manager (VCRM). 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-8514/ (Markdown: https://insights.sbomify.com/CVE-2016-8514/index.md)
```

## Sources

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

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