# CVE-2016-9346: Information disclosure in Moxa MiiNePort

> Attackers can read unencrypted configuration data from Moxa MiiNePort devices, potentially exposing sensitive network settings.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2j26-x5fv-jr5f

## What is CVE-2016-9346?

CVE-2016-9346 is a medium-severity vulnerability in Moxa MiiNePort, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Moxa MiiNePort E1 versions prior to 1.8, E2 versions prior to 1.4, and E3 versions prior to 1.1. Configuration data are stored in a file that is not encrypted.

Weakness: CWE-310

## Which versions are affected by CVE-2016-9346?

It affects 3 products.


Products: Moxa Miineport E1 Firmware, Moxa Miineport E2 Firmware, Moxa Miineport E3 Firmware.

## How do I fix CVE-2016-9346?

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

## Is CVE-2016-9346 being exploited?

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

## Other vulnerabilities in Moxa MiiNePort

- [CVE-2023-28697](https://insights.sbomify.com/CVE-2023-28697/): Moxa MiiNePort E1 - Broken Access Control (critical 9.8)
- [CVE-2016-9344](https://insights.sbomify.com/CVE-2016-9344/): Information disclosure in Moxa MiiNePort (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9346 and fix it if it is affected.

What it is: CVE-2016-9346 is a medium-severity vulnerability in Moxa MiiNePort, published on 13 Feb 2017. 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-2016-9346 in the wild and no public exploit code.

Affected product: Moxa MiiNePort. 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-2016-9346/ (Markdown: https://insights.sbomify.com/CVE-2016-9346/index.md)
```

## Sources

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

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