# CVE-2021-22357: Denial of service in S12700;S5700;S6700;S7700

> Attackers can cause denial of service on Huawei switches by sending specific messages due to insufficient input validation.

- **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:** 23 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w9mq-c2pg-qc2x

## What is CVE-2021-22357?

CVE-2021-22357 is a high-severity denial of service vulnerability in S12700;S5700;S6700;S7700, published on 23 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a denial of service vulnerability in Huawei products. A module cannot deal with specific messages due to validating inputs insufficiently. Attackers can exploit this vulnerability by sending specific messages to affected module. This can cause denial of service. Affected product versions include: S12700 V200R013C00SPC500, V200R019C00SPC500; S5700 V200R013C00SPC500, V200R019C00SPC500; S6700 V200R013C00SPC500, V200R019C00SPC500; S7700 V200R013C00SPC500, V200R019C00SPC500.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 4 products.


Products: Huawei S12700 Firmware, Huawei S5700 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware.

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

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

## Is CVE-2021-22357 being exploited?

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

## Other vulnerabilities in S12700;S5700;S6700;S7700

- [CVE-2016-4087](https://insights.sbomify.com/CVE-2016-4087/): Command injection in n/a (high 8.1)
- [CVE-2019-19397](https://insights.sbomify.com/CVE-2019-19397/): Weak cryptography in S12700;S1700;S2700;S5700;S6700;S7700;S9700 (high 7.5)
- [CVE-2019-5285](https://insights.sbomify.com/CVE-2019-5285/): Denial of service in S12700, S12700, S12700, S12700, S12700, S12700, S12700, S12700, S1700, S1700, S1700, S1700, S1700, S1700, S2300, S2300, S2300, S2300, S2300, S2300, S2300, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S5300, S5300, S5300, S5300, S5300, S5300, S5300, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S600-E, S600-E, S600-E, S600-E, S600-E, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7900, S7900, S7900, S9300, S9300, S9300, S9300, S9300, S9300, S9300, S9300X, S9300X, S9300X, S9300X, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700 (high 7.5)
- [CVE-2016-8786](https://insights.sbomify.com/CVE-2016-8786/): Denial of service in S12700, S5700, S6700, S7700, S9700 (high 7.5)
- [CVE-2017-17300](https://insights.sbomify.com/CVE-2017-17300/): Integer overflow in S12700,S5700,S6700,S7700,S9700 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22357 is a high-severity denial of service vulnerability in S12700;S5700;S6700;S7700, published on 23 Aug 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-22357 in the wild and no public exploit code.

Affected product: S12700;S5700;S6700;S7700. 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-22357/ (Markdown: https://insights.sbomify.com/CVE-2021-22357/index.md)
```

## Sources

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

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