CVE-2017-10935
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 · uneditedAll versions prior to ZSRV2 V3.00.40 of the ZTE ZXR10 1800-2S products allow remote authenticated users to bypass the original password authentication protection to change other user's password.
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 ZTE ZXR10 1800-2S router's web management interface contains an authentication bypass vulnerability in the password change functionality. Authenticated users can manipulate the password reset mechanism to change passwords of other users without proper authorization, enabling privilege escalation from standard user to administrator accounts.
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.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 device modelAccess the router's web management interface or CLI and locate the system information page to confirm the device is a ZTE ZXR10 1800-2S. This is typically found under Status > System Info or via CLI command 'show system-info'.Affected if The device model matches ZTE ZXR10 1800-2S
-
Check the installed firmware versionIn the web interface, navigate to Status > System Info or Administration > Firmware Upgrade to view the current firmware version. Alternatively, use CLI command 'show version' or 'show firmware-version' if telnet/SSH access is available.Affected if The firmware version is below 3.00.40 (for example, 3.00.30, 2.x.x, etc.)
-
Verify web management interface is enabledCheck if the HTTP/HTTPS web management interface is active by attempting to access the router's IP address in a browser (commonly http://192.168.1.1). Also verify via CLI using 'show ip http' or 'show web-service status'.Affected if The web management interface is accessible and enabled on the device
-
Confirm multiple user accounts existIn the web interface, go to Administration > User Management or Administration > Account Settings to list all configured users. In CLI, use 'show users' or 'show accounting' commands.Affected if Two or more user accounts are configured on the device, providing potential targets for unauthorized password modification
The device is affected if it is a ZTE ZXR10 1800-2S router running firmware version below 3.00.40 with the web management interface enabled and multiple user accounts present.
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 device firmware to ZSRV2 V3.00.40 or later to obtain the vendor patch. If immediate upgrade is not feasible, limit web management interface access to trusted IP addresses only and monitor authentication logs for unauthorized password modification attempts.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10935 — 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-10935 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