# CVE-2021-22356: Weak cryptography in IPS Module;NGFW Module;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500

> Attackers can capture and analyze network traffic to obtain sensitive information due to the use of a weak cryptographic algorithm in Huawei firewall modules.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hj8f-mh7g-pc82

## What is CVE-2021-22356?

CVE-2021-22356 is a medium-severity vulnerability in Huawei Ips Module Firmware, published on 23 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a weak secure algorithm vulnerability in Huawei products. A weak secure algorithm is used in a module. Attackers can exploit this vulnerability by capturing and analyzing the messages between devices to obtain information. This can lead to information leak.Affected product versions include: IPS Module V500R005C00SPC100, V500R005C00SPC200; NGFW Module V500R005C00SPC100, V500R005C00SPC200; Secospace USG6300 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; Secospace USG6500 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; Secospace USG6600 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; USG9500 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 6 products.


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

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

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

## Is CVE-2021-22356 being exploited?

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

What it is: CVE-2021-22356 is a medium-severity vulnerability in Huawei Ips Module Firmware, published on 23 Nov 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-22356 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-2021-22356/ (Markdown: https://insights.sbomify.com/CVE-2021-22356/index.md)
```

## Sources

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

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