CVE-2017-10931
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 · uneditedThe ZXR10 1800-2S before v3.00.40 incorrectly restricts the download of the file directory range for WEB users, resulting in the ability to download any files and cause information leaks such as system configuration.
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 ZXR10 1800-2S router before version 3.00.40 contains a path traversal vulnerability in its web interface that allows authenticated WEB users to bypass intended directory restrictions and download arbitrary files from the device's filesystem, leading to exposure of sensitive system configuration and other confidential data.
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.00.40< 3.00.40< 3.00.40< 3.00.40CVSS 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.
-
Identify the device modelAccess the router web interface or check the device label/menu for the exact model number (e.g., ZXR10 1800-2S, 2800-4, 3800-8, or 160)Affected if The device is one of the listed ZXR10 models
-
Check the installed firmware versionLog into the router web interface and navigate to the System Info or Maintenance section to view the firmware version, or use the command line and run 'show version' or similarAffected if The firmware version is lower than 3.00.40 (e.g., 3.00.30, 3.00.25, etc.)
-
Verify if the web management interface is enabledCheck the router configuration for HTTP/HTTPS web interface settings, typically found under Administration or Security settingsAffected if The web interface is enabled and accessible over the network
-
Check web service accessibilityAttempt to access the router's web interface from a network perspective - verify port 80 or 443 is listening and reachableAffected if The web service is exposed on the network (even if behind NAT)
-
Review authentication configurationCheck if default or any web management credentials are configured and in use for the router's admin panelAffected if Valid credentials exist for the web interface (any user account with web access)
If the device is a ZTE ZXR10 model (1800-2S, 2800-4, 3800-8, or 160) running firmware version below 3.00.40 and the web interface is enabled with accessible credentials, the environment is affected by this path traversal vulnerability.
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.00.40
Upgrade the ZXR10 1800-2S firmware to version 3.00.40 or later to obtain the vendor patch. If immediate upgrade is not feasible, restrict network access to the device's web management interface to trusted networks or IP addresses using ACLs.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10931 — 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-2017-10931 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