# CVE-2020-1816: Denial of service in NIP6800

> Remote attackers can cause denial of service in IPSec functions by sending crafted IPSEC packets to Huawei network security devices.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 17 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9gm6-wwwg-m956

## What is CVE-2020-1816?

CVE-2020-1816 is a high-severity denial of service vulnerability in Huawei Nip6800 Firmware, published on 17 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00 have a Denial of Service (DoS) vulnerability. Due to improper processing of specific IPSEC packets, remote attackers can send constructed IPSEC packets to affected devices to exploit this vulnerability. Successful exploit could cause the IPSec function of the affected device abnormal.

## Which versions are affected by CVE-2020-1816?

It affects 3 products.


Products: Huawei Nip6800 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Usg9500 Firmware.

## How do I fix CVE-2020-1816?

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

## Is CVE-2020-1816 being exploited?

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

## Other vulnerabilities in Huawei Nip6800 Firmware

- [CVE-2020-1860](https://insights.sbomify.com/CVE-2020-1860/): Auth bypass in NIP6800;Secospace USG6600;USG9500 (high 7.5)
- [CVE-2020-1873](https://insights.sbomify.com/CVE-2020-1873/): Denial of service in NIP6800;Secospace USG6600;USG9500 (high 7.5)
- [CVE-2020-1876](https://insights.sbomify.com/CVE-2020-1876/): Memory corruption in NIP6800;Secospace USG6600;USG9500 (high 7.5)
- [CVE-2020-1881](https://insights.sbomify.com/CVE-2020-1881/): Denial of service in NIP6800;Secospace USG6600;USG9500 (high 7.5)
- [CVE-2020-1815](https://insights.sbomify.com/CVE-2020-1815/): Denial of service in NIP6800 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1816 and fix it if it is affected.

What it is: CVE-2020-1816 is a high-severity denial of service vulnerability in Huawei Nip6800 Firmware, published on 17 Feb 2020. 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-2020-1816 in the wild and no public exploit code.

Affected product: Huawei Nip6800 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-2020-1816/ (Markdown: https://insights.sbomify.com/CVE-2020-1816/index.md)
```

## Sources

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

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