# CVE-2021-22359: Denial of service in S5700;S6700

> An attacker can cause service disruption on Huawei S5700 and S6700 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:** 27 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qmm3-r49c-cwh6

## What is CVE-2021-22359?

CVE-2021-22359 is a high-severity denial of service vulnerability in S5700;S6700, published on 27 May 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 the verisions V200R005C00SPC500 of S5700 and V200R005C00SPC500 of S6700. An attacker could exploit this vulnerability by sending specific message to a targeted device. Due to insufficient input validation, successful exploit can cause the service abnormal.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Huawei S5700 Firmware, Huawei S6700 Firmware.

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

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

## Is CVE-2021-22359 being exploited?

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

## Other vulnerabilities in S5700;S6700

- [CVE-2017-15324](https://insights.sbomify.com/CVE-2017-15324/): Denial of service in S12700 (high 7.5)
- [CVE-2019-5290](https://insights.sbomify.com/CVE-2019-5290/): Null dereference in S5700;S6700 (medium 6.5)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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