CVE-2020-6875
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 · uneditedA ZTE product is impacted by the improper access control vulnerability. Due to lack of an authentication protection mechanism in the program, attackers could use this vulnerability to gain access right through brute-force attacks. This affects: <ZXONE 19700 SNPE><ZXONE8700V1.40R2B13_SNPE>
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 confidenceThis is an improper access control vulnerability in ZTE optical networking products (ZXONE 19700 SNPE and ZXONE8700V1.40R2B13_SNPE). The devices lack authentication protection mechanisms, allowing attackers to perform brute-force attacks to guess credentials and gain unauthorized access to the system. This is a critical network-exploitable vulnerability requiring no authentication to attempt exploitation.
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= zxone8700v1.40r2b13_snpeCVSS 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 device modelLog into the device CLI or check the system information page to confirm the model is ZXONE 19700 SNPE or ZXONE 8700Affected if The model is ZXONE 19700 SNPE or ZXONE 8700
-
Check the firmware versionRun the command to display firmware version (typically 'show version' or check system info), and compare to the affected version zxone8700v1.40r2b13_snpeAffected if The firmware version matches exactly zxone8700v1.40r2b13_snpe
-
Determine if web management interface is exposed to networkCheck the network configuration for the management interface IP address and whether it is reachable from untrusted networksAffected if The web management interface (HTTP/HTTPS) is accessible from an untrusted network segment
-
Verify if authentication protection exists for the login pageInspect the login page response headers and check if there are any authentication challenges (HTTP 401, WWW-Authenticate) or rate limiting headers before reaching the login formAffected if No HTTP authentication challenge is presented and the login form is directly accessible without any prior authentication barrier
If the device is a ZXONE 19700 SNPE or ZXONE 8700 with firmware version zxone8700v1.40r2b13_snPE and its management interface is network-accessible, the environment is affected because the device lacks authentication protection mechanisms.
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 dataImplement a robust authentication mechanism with brute-force protection (rate limiting, account lockout after failed attempts) on all access points. Enforce strong password policies and consider implementing multi-factor authentication if supported.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6875 — 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-2020-6875 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