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

> Remote attackers can read configuration and log files from Moxa Secure Router devices via a crafted URL.

- **Severity:** High 7.5 (`CVSS:3.1/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-8gqr-f87p-7vm9

## What is CVE-2016-0875?

CVE-2016-0875 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 Secure Router EDR-G903 devices before 3.4.12 allow remote attackers to read configuration and log files via a crafted URL.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Moxa Edr-G903 Firmware.

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

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

## Is CVE-2016-0875 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-0876](https://insights.sbomify.com/CVE-2016-0876/): Information disclosure in n/a (high 7.5)
- [CVE-2016-0877](https://insights.sbomify.com/CVE-2016-0877/): Denial of service in n/a (high 7.5)
- [CVE-2016-0878](https://insights.sbomify.com/CVE-2016-0878/): Denial of service in n/a (high 7.5)
- [CVE-2016-0879](https://insights.sbomify.com/CVE-2016-0879/): Information disclosure in n/a (high 7.5)
- [CVE-2012-4712](https://insights.sbomify.com/CVE-2012-4712/): Hardcoded credentials in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-0875 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-0875 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-0875/ (Markdown: https://insights.sbomify.com/CVE-2016-0875/index.md)
```

## Sources

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

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