# CVE-2020-9067: Memory corruption in SmartAX EA5800

> A buffer overflow in Huawei OLT devices allows remote attackers to execute arbitrary code on the affected network equipment.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 2 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g4g6-2v6v-6j9q

## What is CVE-2020-9067?

CVE-2020-9067 is a high-severity memory corruption vulnerability in SmartAX EA5800, published on 2 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a buffer overflow vulnerability in some Huawei products. The vulnerability can be exploited by an attacker to perform remote code execution on the affected products when the affected product functions as an optical line terminal (OLT). Affected product versions include:SmartAX MA5600T versions V800R013C10, V800R015C00, V800R015C10, V800R017C00, V800R017C10, V800R018C00, V800R018C10; SmartAX MA5800 versions V100R017C00, V100R017C10, V100R018C00, V100R018C10, V100R019C10; SmartAX EA5800 versions V100R018C00, V100R018C10, V100R019C10.

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

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

It affects 3 products.


Products: Huawei Smartax Ea5800 Firmware, Huawei Smartax Ma5600t Firmware, Huawei Smartax Ma5800 Firmware.

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

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

## Is CVE-2020-9067 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9067 is a high-severity memory corruption vulnerability in SmartAX EA5800, published on 2 Apr 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-9067 in the wild and no public exploit code.

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

## Sources

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

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