# CVE-2016-8797: Denial of service in AR3200,S12700,S5300,S5700,S6300,S6700,S7700,S9300,S9700 AR3200 V200R007C00, V200R005C32, V200R005C20,S12700 V200R008C00, V200R007C00,S5300 V200R008C00, V200R007C00, V200R006C00,S5700 V200R008C00, V200R007C00, V200R006C00,S6300 V200R008C00, V200R007C00,S6700 V200R008C00, V200R007C00,S7700 V200R008C00, V200R007C00, V200R006C00,S9300 V200R008C00, V200R007C00, V200R006C00,S9700 V200R008C00, V200R007C00, V200R006C00,

> Remote attackers can cause memory exhaustion and denial of service on Huawei network devices by sending abnormal MPLS packets.

- **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:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c58w-fvhw-g742

## What is CVE-2016-8797?

CVE-2016-8797 is a high-severity denial of service vulnerability in Huawei Ar3200 Firmware, published on 2 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei AR3200 with software V200R007C00, V200R005C32, V200R005C20; S12700 with software V200R008C00, V200R007C00; S5300 with software V200R008C00, V200R007C00, V200R006C00; S5700 with software V200R008C00, V200R007C00, V200R006C00; S6300 with software V200R008C00, V200R007C00; S6700 with software V200R008C00, V200R007C00; S7700 with software V200R008C00, V200R007C00, V200R006C00; S9300 with software V200R008C00, V200R007C00, V200R006C00; and S9700 with software V200R008C00, V200R007C00, V200R006C00 allow remote attackers to send abnormal Multiprotocol Label Switching (MPLS) packets to cause memory exhaustion.

Weakness: CWE-399

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

It affects 9 products.


Products: Huawei Ar3200 Firmware, Huawei S12700 Firmware, Huawei S5300 Firmware, Huawei S5700 Firmware, Huawei S6300 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware, Huawei S9300 Firmware, Huawei S9700 Firmware.

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

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

## Is CVE-2016-8797 being exploited?

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

## Other vulnerabilities in Huawei Ar3200 Firmware

- [CVE-2020-9068](https://insights.sbomify.com/CVE-2020-9068/): Auth bypass in AR3200 (critical 9.8)
- [CVE-2016-6206](https://insights.sbomify.com/CVE-2016-6206/): Other in n/a (critical 9.8)
- [CVE-2017-15341](https://insights.sbomify.com/CVE-2017-15341/): Denial of service in AR3200,TE40,TE50,TE60 (high 7.5)
- [CVE-2016-5368](https://insights.sbomify.com/CVE-2016-5368/): Denial of service in n/a (high 7.5)
- [CVE-2016-3950](https://insights.sbomify.com/CVE-2016-3950/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8797 is a high-severity denial of service vulnerability in Huawei Ar3200 Firmware, published on 2 Apr 2017. 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-8797 in the wild and no public exploit code.

Affected product: Huawei Ar3200 Firmware. 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-8797/ (Markdown: https://insights.sbomify.com/CVE-2016-8797/index.md)
```

## Sources

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

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