# CVE-2020-1821: Memory corruption in IPS Module

> Out-of-bounds read in Huawei network devices allows attackers to disrupt service via malicious packets.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2024
- **Updated:** 30 Dec 2024
- **Also known as:** GHSA-866j-7c9v-5xf7

## What is CVE-2020-1821?

CVE-2020-1821 is a low-severity memory corruption vulnerability in Huawei Ips Module Firmware, published on 28 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. The specific decoding function may occur out-of-bounds read when processes an incoming data packet. Successful exploit of these vulnerabilities may disrupt service on the affected device. (Vulnerability ID: HWPSIRT-2018-12275,HWPSIRT-2018-12276,HWPSIRT-2018-12277,HWPSIRT-2018-12278,HWPSIRT-2018-12279,HWPSIRT-2018-12280 and HWPSIRT-2018-12289)

The seven vulnerabilities have been assigned seven Common Vulnerabilities and Exposures (CVE) IDs: CVE-2020-1818, CVE-2020-1819, CVE-2020-1820, CVE-2020-1821, CVE-2020-1822, CVE-2020-1823 and CVE-2020-1824.

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

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

It affects 9 products.


Products: Huawei Ips Module Firmware, Huawei Ngfw Module Firmware, Huawei Nip6300 Firmware, Huawei Nip6600 Firmware, Huawei Nip6800 Firmware, Huawei Secospace Usg6300 Firmware, Huawei Secospace Usg6500 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Usg6000v Firmware.

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

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

## Is CVE-2020-1821 being exploited?

There is no known exploitation of CVE-2020-1821 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-2016-4576](https://insights.sbomify.com/CVE-2016-4576/): Memory corruption in n/a (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1821 is a low-severity memory corruption vulnerability in Huawei Ips Module Firmware, published on 28 Dec 2024. 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-1821 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-2020-1821/ (Markdown: https://insights.sbomify.com/CVE-2020-1821/index.md)
```

## Sources

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

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