# CVE-2020-6999: Memory corruption in Moxa EDS-G516E Series firmware, Version 5.2 or lower

> Buffer overflow in Moxa EDS-G516E firmware allows attackers to execute arbitrary code or cause denial of service via crafted parameters.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4348-9j97-6mhj

## What is CVE-2020-6999?

CVE-2020-6999 is a medium-severity memory corruption vulnerability in Moxa EDS-G516E Series firmware, Version 5.2 or lower, published on 26 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Moxa EDS-G516E Series firmware, Version 5.2 or lower, some of the parameters in the setting pages do not ensure text is the correct size for its buffer.

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

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

It affects 1 product.


Products: Moxa Mds-G516e Firmware.

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

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

## Is CVE-2020-6999 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6999 is a medium-severity memory corruption vulnerability in Moxa EDS-G516E Series firmware, Version 5.2 or lower, published on 26 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6999 in the wild and no public exploit code.

Affected product: Moxa EDS-G516E Series firmware, Version 5.2 or lower. 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-6999/ (Markdown: https://insights.sbomify.com/CVE-2020-6999/index.md)
```

## Sources

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

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