# CVE-2018-10694: Information disclosure in n/a

> An attacker can sniff unencrypted Wi-Fi traffic to steal credentials and perform man-in-the-middle attacks on Moxa AWK-3121 devices.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wp8r-cvvg-9jf3

## What is CVE-2018-10694?

CVE-2018-10694 is a high-severity vulnerability in n/a, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Moxa AWK-3121 1.14 devices. The device provides a Wi-Fi connection that is open and does not use any encryption mechanism by default. An administrator who uses the open wireless connection to set up the device can allow an attacker to sniff the traffic passing between the user's computer and the device. This can allow an attacker to steal the credentials passing over the HTTP connection as well as TELNET traffic. Also an attacker can MITM the response and infect a user's computer very easily as well.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Moxa Awk-3121 Firmware.

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

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

## Is CVE-2018-10694 being exploited?

There is no known exploitation of CVE-2018-10694 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-10693](https://insights.sbomify.com/CVE-2018-10693/): Memory corruption in n/a (high 8.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)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10694 is a high-severity vulnerability in n/a, published on 7 Jun 2019. 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-2018-10694 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-10694/ (Markdown: https://insights.sbomify.com/CVE-2018-10694/index.md)
```

## Sources

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

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