# CVE-2016-8798: Security feature bypass in USG5500 V300R001C00 and V300R001C00

> Attackers can bypass the anti-DDoS module on Huawei USG5500 firewalls to cause denial of service on backend servers.

- **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-3x33-4vmh-52pp

## What is CVE-2016-8798?

CVE-2016-8798 is a high-severity vulnerability in USG5500 V300R001C00 and V300R001C00, 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 USG5500 with software V300R001C00 and V300R001C00 allows attackers to bypass the anti-DDoS module of the USGs to cause a denial of service condition on the backend server.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Huawei Usg5500 Firmware.

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

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

## Is CVE-2016-8798 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8798 is a high-severity vulnerability in USG5500 V300R001C00 and V300R001C00, 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-8798 in the wild and no public exploit code.

Affected product: USG5500 V300R001C00 and V300R001C00. 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-8798/ (Markdown: https://insights.sbomify.com/CVE-2016-8798/index.md)
```

## Sources

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

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