CVE-2017-10930
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 access to a resource from an unauthorized actor, resulting in ordinary users being able to download configuration files to steal information like administrator accounts and passwords.
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 · moderate confidenceThe ZXR10 1800-2S has an authorization bypass vulnerability where regular (non-privileged) users can access and download configuration files that contain sensitive information including administrator account credentials and passwords, due to improper access control restrictions in versions before v3.00.40.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 router model and firmware versionLog into the ZXR10 router web interface or CLI and locate the system information or firmware version (typically under Status > System, or via 'show version' command)Affected if The device model is ZXR10 1800-2S, 2800-4, 3800-8, or 160 and the firmware version is less than 3.00.40
-
Verify configuration file download is accessibleLog in with a non-privileged (regular) user account and attempt to access the configuration file download feature in the web interface or via the backup/restore configuration functionAffected if Non-privileged users can access and download the configuration file without requiring elevated privileges
-
Check if configuration contains sensitive credentialsOpen the downloaded configuration file and search for plaintext passwords, username entries, or administrator account credentialsAffected if The configuration file contains administrator usernames and passwords in plaintext
If the device runs firmware version below 3.00.40 AND non-privileged users can download configuration files containing plaintext credentials, the environment is affected by CVE-2017-10930.
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.
dbcve · scoped3.00.40
Upgrade the ZXR10 1800-2S firmware to version v3.00.40 or later to implement proper access controls and prevent unauthorized configuration file downloads.
Firmware version 3.00.40 or later
- 1. Identify the current firmware version of the ZXR10 device by accessing the web management interface or CLI
- 2. If the firmware version is below 3.00.40, download the firmware version 3.00.40 or later from the official ZTE support portal (support.zte.com.cn)
- 3. Upload the new firmware through the device's web management interface under System > Firmware Upgrade, or via CLI using the firmware upgrade command
- 4. After upgrade, verify the new firmware version is 3.00.40 or higher
- 5. Confirm that the vulnerability is remediated by verifying that ordinary users can no longer access configuration files containing administrator credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10930 — 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-10930 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