# CVE-2016-8786: Denial of service in S12700, S5700, S6700, S7700, S9700

> Remote attackers can cause device restarts by sending malformed RSVP packets due to insufficient input validation in Huawei switches.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v32r-xrgh-2vx8

## What is CVE-2016-8786?

CVE-2016-8786 is a high-severity denial of service vulnerability in Huawei Technologies Co., Ltd. S12700, S5700, S6700, S7700, S9700, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei S12700 V200R005C00, V200R006C00, V200R007C00, V200R008C00, S5700 V200R006C00, V200R007C00, V200R008C00, S6700 V200R008C00, S7700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, S9700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00 have a denial of service (DoS) vulnerability. Due to the lack of input validation, a remote attacker may craft a malformed Resource Reservation Protocol (RSVP) packet and send it to the device, causing a few buffer overflows and occasional device restart.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 5 products.


Products: Huawei S12700 Firmware, Huawei S5700 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware, Huawei S9700 Firmware.

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

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

## Is CVE-2016-8786 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. S12700, S5700, S6700, S7700, S9700

- [CVE-2016-4087](https://insights.sbomify.com/CVE-2016-4087/): Command injection in n/a (high 8.1)
- [CVE-2021-22357](https://insights.sbomify.com/CVE-2021-22357/): Denial of service in S12700;S5700;S6700;S7700 (high 7.5)
- [CVE-2019-19397](https://insights.sbomify.com/CVE-2019-19397/): Weak cryptography in S12700;S1700;S2700;S5700;S6700;S7700;S9700 (high 7.5)
- [CVE-2019-5285](https://insights.sbomify.com/CVE-2019-5285/): Denial of service in S12700, S12700, S12700, S12700, S12700, S12700, S12700, S12700, S1700, S1700, S1700, S1700, S1700, S1700, S2300, S2300, S2300, S2300, S2300, S2300, S2300, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S5300, S5300, S5300, S5300, S5300, S5300, S5300, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S600-E, S600-E, S600-E, S600-E, S600-E, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7900, S7900, S7900, S9300, S9300, S9300, S9300, S9300, S9300, S9300, S9300X, S9300X, S9300X, S9300X, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700 (high 7.5)
- [CVE-2017-17300](https://insights.sbomify.com/CVE-2017-17300/): Integer overflow in S12700,S5700,S6700,S7700,S9700 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8786 is a high-severity denial of service vulnerability in Huawei Technologies Co., Ltd. S12700, S5700, S6700, S7700, S9700, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-8786 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. S12700, S5700, S6700, S7700, S9700. 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-8786/ (Markdown: https://insights.sbomify.com/CVE-2016-8786/index.md)
```

## Sources

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

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