# CVE-2020-1866: Memory corruption in NIP6800;S12700;S2700;S5700;S6700;S7700;S9700;Secospace USG6600;USG9500

> Attackers can cause service disruption by sending crafted DHCP messages that trigger an out-of-bounds read in Huawei network devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xf3h-cpcr-5vv3

## What is CVE-2020-1866?

CVE-2020-1866 is a medium-severity memory corruption vulnerability in Huawei Nip6800 Firmware, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an out-of-bounds read vulnerability in several products. The software reads data past the end of the intended buffer when parsing certain crafted DHCP messages. Successful exploit could cause certain service abnormal. Affected product versions include:NIP6800 versions V500R001C30,V500R001C60SPC500,V500R005C00;S12700 versions V200R008C00;S2700 versions V200R008C00;S5700 versions V200R008C00;S6700 versions V200R008C00;S7700 versions V200R008C00;S9700 versions V200R008C00;Secospace USG6600 versions V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500,V500R005C00;USG9500 versions V500R001C30SPC300,V500R001C30SPC600,V500R001C60SPC500,V500R005C00.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 9 products.


Products: Huawei Nip6800 Firmware, Huawei S12700 Firmware, Huawei S2700 Firmware, Huawei S5700 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware, Huawei S9700 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Usg9500 Firmware.

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

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

## Is CVE-2020-1866 being exploited?

There is no known exploitation of CVE-2020-1866 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-1866 and fix it if it is affected.

What it is: CVE-2020-1866 is a medium-severity memory corruption vulnerability in Huawei Nip6800 Firmware, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1866 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-1866/ (Markdown: https://insights.sbomify.com/CVE-2020-1866/index.md)
```

## Sources

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

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