# CVE-2021-22366: Memory corruption in eSE620X vESS

> An out-of-bounds read in Huawei eSE620X vESS allows attackers to cause a Denial of Service by sending crafted internal messages.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-35fw-8rmc-f2j5

## What is CVE-2021-22366?

CVE-2021-22366 is a medium-severity memory corruption vulnerability in eSE620X vESS, published on 22 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an out-of-bounds read vulnerability in eSE620X vESS V100R001C10SPC200, V100R001C20SPC200, V200R001C00SPC300. The vulnerability is due to a function that handles an internal message contains an out-of-bounds read vulnerability. An attacker could crafted messages between system process, successful exploit could cause Denial of Service (DoS).

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

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

It affects 1 product.


Products: Huawei Ese620x Vess Firmware.

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

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

## Is CVE-2021-22366 being exploited?

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

## Other vulnerabilities in eSE620X vESS

- [CVE-2021-39999](https://insights.sbomify.com/CVE-2021-39999/): Memory corruption in eSE620X vESS (high 7.5)
- [CVE-2021-22365](https://insights.sbomify.com/CVE-2021-22365/): Memory corruption in eSE620X vESS (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22366 is a medium-severity memory corruption vulnerability in eSE620X vESS, published on 22 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22366 in the wild and no public exploit code.

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

## Sources

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

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