# CVE-2016-2405: Privilege escalation in n/a

> Remote authenticated users can gain privileges and cause a system crash in Huawei Policy Center via a crafted URL.

- **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:** 12 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2xj7-89p7-g3rh

## What is CVE-2016-2405?

CVE-2016-2405 is a high-severity vulnerability in n/a, published on 12 Apr 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Huawei Policy Center with software before V100R003C10SPC020 allows remote authenticated users to gain privileges and cause a denial of service (system crash) via a crafted URL.

Weakness: CWE-264

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

It affects 1 product.


Products: Huawei Policy Center Firmware.

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

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

## Is CVE-2016-2405 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-3675](https://insights.sbomify.com/CVE-2016-3675/): SQL injection in n/a (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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