# CVE-2016-4576: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via crafted packets in Huawei firewall modules.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 23 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fjg3-w56q-6wxp

## What is CVE-2016-4576?

CVE-2016-4576 is a critical memory corruption vulnerability in Huawei Ips Module Firmware, published on 23 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Application Specific Packet Filtering (ASPF) functionality in the Huawei IPS Module, NGFW Module, NIP6300, NIP6600, Secospace USG6300, USG6500, USG6600, USG9500, and AntiDDoS8000 devices with software before V500R001C20SPC100 allows remote attackers to cause a denial of service or execute arbitrary code via a crafted packet, related to "illegitimate parameters."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 9 products.


Products: Huawei Ips Module Firmware, Huawei Ngfw Module Firmware, Huawei Nip6300 Firmware, Huawei Nip6600 Firmware, Huawei Secospace Antiddos8000 Firmware, Huawei Secospace Usg6300 Firmware, Huawei Secospace Usg6500 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Usg9500 Firmware.

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

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

## Is CVE-2016-4576 being exploited?

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

## Other vulnerabilities in Huawei Ips Module Firmware

- [CVE-2020-9099](https://insights.sbomify.com/CVE-2020-9099/): Auth bypass in IPS Module; NGFW Module; NIP6300; NIP6600; NIP6800; Secospace USG6300; Secospace USG6500; Secospace USG6600; USG9500 (critical 9.8)
- [CVE-2021-37129](https://insights.sbomify.com/CVE-2021-37129/): Memory corruption in IIPS Module;NGFW Module;NIP6600;S12700;S1700;S2700;S5700;S6700;S7700;S9700;USG9500 (high 7.5)
- [CVE-2021-22320](https://insights.sbomify.com/CVE-2021-22320/): Denial of service in IPS Module;NGFW Module;NIP6600;NIP6800;Secospace USG6300;Secospace USG6500;Secospace USG6600 (high 7.5)
- [CVE-2017-15348](https://insights.sbomify.com/CVE-2017-15348/): Denial of service in IPS Module,NGFW Module,NIP6300,NIP6600,Secospace USG6300,Secospace USG6500,Secospace USG6600,USG9500, (high 7.5)
- [CVE-2017-17153](https://insights.sbomify.com/CVE-2017-17153/): Denial of service in IPS,Module,NGFW,Module,NIP6300,NIP6600,Secospace,USG6300,Secospace,USG6500,Secospace,USG6600,USG9500 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4576 is a critical memory corruption vulnerability in Huawei Ips Module Firmware, published on 23 May 2016. 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-4576 in the wild and no public exploit code.

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

## Sources

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

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