CVE-2016-0875
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMoxa Secure Router EDR-G903 devices before 3.4.12 allow remote attackers to read configuration and log files via a crafted URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Moxa Secure Router EDR-G903 devices before version 3.4.12 contain a path traversal vulnerability in the web interface that allows remote unauthenticated attackers to read sensitive configuration and log files via a crafted URL. This exposure could reveal system credentials, network settings, and operational logs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.4.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is EDR-G903Access the device's web interface or check the physical label/console output to verify the exact model number matches 'Moxa EDR-G903'Affected if The device is not an EDR-G903 model, then it is not affected by this specific CVE
-
Check installed firmware versionLog into the device's web interface and navigate to the System > Firmware or Status page to view the current firmware version, or use the console/CLI command to query the firmware versionAffected if The installed firmware version is less than 3.4.12 (for example, 3.4.10, 3.3.x, or any version before 3.4.12)
-
Verify web management interface is enabledCheck the device configuration to confirm the web interface (HTTP/HTTPS) is currently enabled and accessible from the networkAffected if The web interface is enabled and reachable - the path traversal vulnerability requires the web interface to be active for exploitation
-
Test for path traversal vulnerabilityUsing a web browser or curl command, attempt to access a known configuration file through the web interface using path traversal sequences such as ../../../../etc/passwd or similar paths to sensitive filesAffected if The device returns file contents or responds differently than expected when using path traversal sequences in the URL, indicating the vulnerability is present
A user is affected if they have a Moxa EDR-G903 device running firmware version before 3.4.12 with the web management interface enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.4.12
Upgrade the EDR-G903 firmware to version 3.4.12 or later to remediate this vulnerability. If immediate patching is not feasible, restrict or disable the web management interface and implement network segmentation to limit exposure.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-0875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data