# CVE-2020-1799: Use after free in E6878-370

> A use-after-free vulnerability in the Huawei E6878-370 web portal allows attackers to execute malicious code via crafted operations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x8g9-h939-cmr5

## What is CVE-2020-1799?

CVE-2020-1799 is a high-severity use after free vulnerability in E6878-370, published on 21 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

E6878-370 with versions of 10.0.3.1(H557SP27C233), 10.0.3.1(H563SP1C00), 10.0.3.1(H563SP1C233) has a use after free vulnerability. The software references memory after it has been freed in certain scenario, the attacker does a series of crafted operations through web portal, successful exploit could cause a use after free condition which may lead to malicious code execution.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2020-1799?

It affects 1 product.


Products: Huawei E6878-370 Firmware.

## How do I fix CVE-2020-1799?

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

## Is CVE-2020-1799 being exploited?

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

## Other vulnerabilities in E6878-370

- [CVE-2020-1832](https://insights.sbomify.com/CVE-2020-1832/): Memory corruption in E6878-370 (high 8.8)
- [CVE-2020-9241](https://insights.sbomify.com/CVE-2020-9241/): Missing authorization in E6878-370 (high 7.0)
- [CVE-2020-9111](https://insights.sbomify.com/CVE-2020-9111/): Denial of service in E6878-370;E6878-870 (medium 4.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1799 and fix it if it is affected.

What it is: CVE-2020-1799 is a high-severity use after free vulnerability in E6878-370, published on 21 May 2020. 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-2020-1799 in the wild and no public exploit code.

Affected product: E6878-370. 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-2020-1799/ (Markdown: https://insights.sbomify.com/CVE-2020-1799/index.md)
```

## Sources

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

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