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

> Remote authenticated users can escalate privileges to perform operations as other users in Huawei VCM due to improper identity and privilege authentication.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-797j-6cf4-3f6f

## What is CVE-2015-8332?

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

### Official description

Huawei Video Content Management (VCM) before V100R001C10SPC001 does not properly "authenticate online user identities and privileges," which allows remote authenticated users to gain privileges and perform a case operation as another user via a crafted message, aka "Horizontal Privilege Escalation Vulnerability."

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Huawei Vcm5010 Firmware, Huawei Vcm5020 Firmware.

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

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

## Is CVE-2015-8332 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-2738](https://insights.sbomify.com/CVE-2017-2738/): Auth bypass in VCM5010 (critical 9.8)
- [CVE-2017-2737](https://insights.sbomify.com/CVE-2017-2737/): File upload in VCM5010 (high 8.8)
- [CVE-2017-2736](https://insights.sbomify.com/CVE-2017-2736/): Command injection in VCM5010 (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8332 is a high-severity vulnerability in n/a, published on 28 Aug 2017. 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-8332 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-8332/ (Markdown: https://insights.sbomify.com/CVE-2015-8332/index.md)
```

## Sources

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

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