# CVE-2018-10693: Memory corruption in n/a

> An attacker can execute arbitrary commands on Moxa AWK-3121 devices via a buffer overflow in the ping functionality's srvName parameter.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j5v6-264g-wgmq

## What is CVE-2018-10693?

CVE-2018-10693 is a high-severity memory corruption vulnerability in n/a, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered on Moxa AWK-3121 1.14 devices. It provides ping functionality so that an administrator can execute ICMP calls to check if the network is working correctly. However, the same functionality allows an attacker to execute commands on the device. The POST parameter "srvName" is susceptible to a buffer overflow. By crafting a packet that contains a string of 516 characters, it is possible for an attacker to execute the attack.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-10693?

It affects 1 product.


Products: Moxa Awk-3121 Firmware.

## How do I fix CVE-2018-10693?

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

## Is CVE-2018-10693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10698](https://insights.sbomify.com/CVE-2018-10698/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-10695](https://insights.sbomify.com/CVE-2018-10695/): Memory corruption in n/a (high 8.8)
- [CVE-2018-10696](https://insights.sbomify.com/CVE-2018-10696/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-10697](https://insights.sbomify.com/CVE-2018-10697/): Command injection in n/a (high 8.8)
- [CVE-2018-10699](https://insights.sbomify.com/CVE-2018-10699/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10693 and fix it if it is affected.

What it is: CVE-2018-10693 is a high-severity memory corruption vulnerability in n/a, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-10693 in the wild and no public exploit code.

Affected product: n/a. 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-2018-10693/ (Markdown: https://insights.sbomify.com/CVE-2018-10693/index.md)
```

## Sources

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

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