# CVE-2015-5413: Privilege escalation in n/a

> Authenticated attackers can escalate privileges and access sensitive information in HP Version Control Repository Manager.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/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:** 26 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f9j3-5jf4-66p6

## What is CVE-2015-5413?

CVE-2015-5413 is a medium-severity vulnerability in n/a, published on 26 Aug 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HP Version Control Repository Manager (VCRM) before 7.5.0 allows remote authenticated users to gain privileges and obtain sensitive information via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2015-5413?

It affects 1 product.


Products: Hp Version Control Repository Manager.

## How do I fix CVE-2015-5413?

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

## Is CVE-2015-5413 being exploited?

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

## Other vulnerabilities in n/a

- [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-2016-8514](https://insights.sbomify.com/CVE-2016-8514/): A remote information disclosure in HPE Version Control Repository Manager (VCRM) was found. (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5413 and fix it if it is affected.

What it is: CVE-2015-5413 is a medium-severity vulnerability in n/a, published on 26 Aug 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5413 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-2015-5413/ (Markdown: https://insights.sbomify.com/CVE-2015-5413/index.md)
```

## Sources

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

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