# CVE-2016-8796: Denial of service in USG9520,USG9560,USG9580, USG9520 V300R001C01,USG9560 V300R001C01,USG9580 V300R001C01

> Unauthenticated attackers can cause a denial of service on Huawei USG firewalls by sending abnormal DHCP request 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-gcp4-p6rh-2cff

## What is CVE-2016-8796?

CVE-2016-8796 is a high-severity denial of service vulnerability in USG9520,USG9560,USG9580, USG9520 V300R001C01,USG9560 V300R001C01,USG9580 V300R001C01, 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 USG9520 V300R001C01, USG9560 V300R001C01, and USG9580 V300R001C01 allow unauthenticated attackers to send abnormal DHCP request packets to the affected products to trigger a DoS condition.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 3 products.


Products: Huawei Usg9520 Firmware, Huawei Usg9560 Firmware, Huawei Usg9580 Firmware.

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

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

## Is CVE-2016-8796 being exploited?

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

## Other vulnerabilities in USG9520,USG9560,USG9580, USG9520 V300R001C01,USG9560 V300R001C01,USG9580 V300R001C01

- [CVE-2014-9697](https://insights.sbomify.com/CVE-2014-9697/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8796 is a high-severity denial of service vulnerability in USG9520,USG9560,USG9580, USG9520 V300R001C01,USG9560 V300R001C01,USG9580 V300R001C01, 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-8796 in the wild and no public exploit code.

Affected product: USG9520,USG9560,USG9580, USG9520 V300R001C01,USG9560 V300R001C01,USG9580 V300R001C01. 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-8796/ (Markdown: https://insights.sbomify.com/CVE-2016-8796/index.md)
```

## Sources

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

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