# CVE-2021-22321: Use after free in NIP6600;NIP6800;S12700;S1700;S2700;S5700;S6700;S7700;S9700;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500

> Attackers can trigger a use-after-free vulnerability in Huawei network devices, causing service disruption and compromising normal operations.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/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:** 22 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p3qf-gvrh-m63f

## What is CVE-2021-22321?

CVE-2021-22321 is a medium-severity use after free vulnerability in Huawei Nip6300 Firmware, published on 22 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a use-after-free vulnerability in a Huawei product. A module cannot deal with specific operations in special scenarios. Attackers can exploit this vulnerability by performing malicious operations. This can cause memory use-after-free, compromising normal service. Affected product include some versions of NIP6300, NIP6600, NIP6800, S1700, S2700, S5700, S6700 , S7700, S9700, Secospace USG6300, Secospace USG6500, Secospace USG6600 and USG9500.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2021-22321?

It affects 14 products.


Products: Huawei Nip6300 Firmware, Huawei Nip6600 Firmware, Huawei Nip6800 Firmware, Huawei S12700 Firmware, Huawei S1700 Firmware, Huawei S2700 Firmware, Huawei S5700 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware, Huawei S9700 Firmware, Huawei Secospace Usg6300 Firmware, Huawei Secospace Usg6500 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Usg9500 Firmware.

## How do I fix CVE-2021-22321?

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

## Is CVE-2021-22321 being exploited?

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

## Other vulnerabilities in Huawei Nip6300 Firmware

- [CVE-2020-1847](https://insights.sbomify.com/CVE-2020-1847/): Denial of service in NIP6300;NIP6600;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500 (high 7.5)
- [CVE-2020-9127](https://insights.sbomify.com/CVE-2020-9127/): Command injection in NIP6300;NIP6600;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500 (medium 6.7)
- [CVE-2017-15315](https://insights.sbomify.com/CVE-2017-15315/): Denial of service in NIP6300,NIP6600,Secospace USG6300,Secospace USG6500 (medium 6.5)
- [CVE-2021-22310](https://insights.sbomify.com/CVE-2021-22310/): Information disclosure in NIP6300;NIP6600;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500 (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22321 and fix it if it is affected.

What it is: CVE-2021-22321 is a medium-severity use after free vulnerability in Huawei Nip6300 Firmware, published on 22 Mar 2021. 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-2021-22321 in the wild and no public exploit code.

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

## Sources

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

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