# CVE-2016-8801: Command injection in OceanStor 5600 V3 V300R003C00C10 and earlier versions

> Administrators can inject commands into specific parameters to execute arbitrary code with root privileges on Huawei OceanStor storage systems.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w8hp-x9c3-2p78

## What is CVE-2016-8801?

CVE-2016-8801 is a high-severity command injection vulnerability in OceanStor 5600 V3 V300R003C00C10 and earlier versions, published on 2 Apr 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Huawei OceanStor 5600 V3 with V300R003C00C10 and earlier versions allows attackers with administrator privilege to inject a command into a specific command's parameters, and run this injected command with root privilege.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Huawei Oceanstor 5600 V3 Firmware.

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

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

## Is CVE-2016-8801 being exploited?

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

## Other vulnerabilities in OceanStor 5600 V3 V300R003C00C10 and earlier versions

- [CVE-2016-8754](https://insights.sbomify.com/CVE-2016-8754/): Hardcoded credentials in OceanStor 5600 V3 V300R003C00 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8801 is a high-severity command injection vulnerability in OceanStor 5600 V3 V300R003C00C10 and earlier versions, published on 2 Apr 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-8801 in the wild and no public exploit code.

Affected product: OceanStor 5600 V3 V300R003C00C10 and earlier versions. 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-8801/ (Markdown: https://insights.sbomify.com/CVE-2016-8801/index.md)
```

## Sources

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

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