# CVE-2016-2295: Information disclosure in n/a

> Remote attackers can read configuration files to obtain sensitive cleartext information from Moxa MiiNePort devices.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 31 May 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j98q-5gf7-hcmc

## What is CVE-2016-2295?

CVE-2016-2295 is a high-severity vulnerability in n/a, published on 31 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Moxa MiiNePort_E1_4641 devices with firmware 1.1.10 Build 09120714, MiiNePort_E1_7080 devices with firmware 1.1.10 Build 09120714, MiiNePort_E2_1242 devices with firmware 1.1 Build 10080614, MiiNePort_E2_4561 devices with firmware 1.1 Build 10080614, and MiiNePort E3 devices with firmware 1.0 Build 11071409 allow remote attackers to obtain sensitive cleartext information by reading a configuration file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 5 products.


Products: Moxa Miineport E1 4641 Firmware, Moxa Miineport E1 7080 Firmware, Moxa Miineport E2 1242 Firmware, Moxa Miineport E2 4561 Firmware, Moxa Miineport E3 Firmware.

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

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

## Is CVE-2016-2295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2285](https://insights.sbomify.com/CVE-2016-2285/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-2286](https://insights.sbomify.com/CVE-2016-2286/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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