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

> A buffer overflow in Huawei eSE620X vESS allows attackers to cause denial of service by sending crafted packets.

- **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:** 11 Jul 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cf47-5h63-vm9m

## What is CVE-2021-39999?

CVE-2021-39999 is a high-severity memory corruption vulnerability in eSE620X vESS, published on 11 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a buffer overflow vulnerability in eSE620X vESS V100R001C10SPC200 and V100R001C20SPC200. An attacker can exploit this vulnerability by sending a specific message to the target device due to insufficient validation of packets. Successful exploit could cause a denial of service condition.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Huawei Ese620x Vess Firmware.

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

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

## Is CVE-2021-39999 being exploited?

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

## Other vulnerabilities in eSE620X vESS

- [CVE-2021-22366](https://insights.sbomify.com/CVE-2021-22366/): Memory corruption in eSE620X vESS (medium 5.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-39999 and fix it if it is affected.

What it is: CVE-2021-39999 is a high-severity memory corruption vulnerability in eSE620X vESS, published on 11 Jul 2022. 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-39999 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-39999/ (Markdown: https://insights.sbomify.com/CVE-2021-39999/index.md)
```

## Sources

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

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