# CVE-2016-8780: Denial of service in CloudEngine 6800, CloudEngine 7800, CloudEngine 8800, CloudEngine 12800 CloudEngine 6800 V100R006C00,CloudEngine 7800 V100R006C00,CloudEngine 8800 V100R006C00,CloudEngine 12800 V100R006C00,

> Remote attackers with specific permissions can exhaust shared storage by storing massive files, causing a denial of service on Huawei CloudEngine switches.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5x9p-jh4v-62pr

## What is CVE-2016-8780?

CVE-2016-8780 is a medium-severity denial of service vulnerability in CloudEngine 6800, CloudEngine 7800, CloudEngine 8800, CloudEngine 12800 CloudEngine 6800 V100R006C00,CloudEngine 7800 V100R006C00,CloudEngine 8800 V100R006C00,CloudEngine 12800 V100R006C00,, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Huawei CloudEngine 6800 V100R006C00, CloudEngine 7800 V100R006C00, CloudEngine 8800 V100R006C00, and CloudEngine 12800 V100R006C00 allow remote attackers with specific permission to store massive files to exhaust the shared storage space, leading to a DoS condition.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 4 products.


Products: Huawei Cloudengine 12800 Firmware, Huawei Cloudengine 6800 Firmware, Huawei Cloudengine 7800 Firmware, Huawei Cloudengine 8800 Firmware.

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

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

## Is CVE-2016-8780 being exploited?

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

## Other vulnerabilities in CloudEngine 6800, CloudEngine 7800, CloudEngine 8800, CloudEngine 12800 CloudEngine 6800 V100R006C00,CloudEngine 7800 V100R006C00,CloudEngine 8800 V100R006C00,CloudEngine 12800 V100R006C00,

- [CVE-2016-6178](https://insights.sbomify.com/CVE-2016-6178/): Other in n/a (critical 9.8)
- [CVE-2020-9207](https://insights.sbomify.com/CVE-2020-9207/): Auth bypass in CloudEngine 12800 (high 7.8)
- [CVE-2021-40008](https://insights.sbomify.com/CVE-2021-40008/): Denial of service in CloudEngine 12800;CloudEngine 5800;CloudEngine 6800;CloudEngine 7800 (high 7.5)
- [CVE-2021-22328](https://insights.sbomify.com/CVE-2021-22328/): Denial of service in CloudEngine 12800;CloudEngine 5800;CloudEngine 6800;CloudEngine 7800 (high 7.5)
- [CVE-2021-22332](https://insights.sbomify.com/CVE-2021-22332/): Use after free in CloudEngine 12800;CloudEngine 5800;CloudEngine 6800;CloudEngine 7800 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8780 is a medium-severity denial of service vulnerability in CloudEngine 6800, CloudEngine 7800, CloudEngine 8800, CloudEngine 12800 CloudEngine 6800 V100R006C00,CloudEngine 7800 V100R006C00,CloudEngine 8800 V100R006C00,CloudEngine 12800 V100R006C00,, published on 2 Apr 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-2016-8780 in the wild and no public exploit code.

Affected product: CloudEngine 6800, CloudEngine 7800, CloudEngine 8800, CloudEngine 12800 CloudEngine 6800 V100R006C00,CloudEngine 7800 V100R006C00,CloudEngine 8800 V100R006C00,CloudEngine 12800 V100R006C00,. 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-8780/ (Markdown: https://insights.sbomify.com/CVE-2016-8780/index.md)
```

## Sources

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

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