CVE-2020-6877
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 an information leak vulnerability. An attacker could use this vulnerability to obtain the authentication password of the handheld terminal and access the device illegally for operation. This affects: ZXA10 eODN V2.3P2T1
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 confidenceZTE ZXA10 eODN V2.3P2T1 contains an information disclosure vulnerability where an attacker can obtain the authentication password of handheld terminals, enabling unauthorized device access. The specific attack vector and mechanism are not detailed in the available advisory.
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= 2.3p2t1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 ZXA10 eODN firmware versionAccess the device management interface or use the command line interface (CLI) to query the firmware version. Common methods include logging into the web-based management portal and navigating to System or Device Information sections, or using SNMP to query the device OID for firmware version.Affected if The displayed firmware version is exactly 2.3P2T1 (case-insensitive match)
-
Confirm the device model is ZTE ZXA10 eODNVerify that the affected device is specifically the ZXA10 eODN model and not another ZTE product line. Check the device label, web interface, or CLI output for the exact model designation.Affected if The device model is confirmed as ZXA10 eODN running firmware version 2.3P2T1
-
Determine if ODN management interfaces are network-accessibleReview network configuration to check if the ODN management interface (typically ports used for handheld terminal provisioning and device management) is exposed to untrusted networks or the internet. Check firewall rules, ACLs, and interface bindings.Affected if The ODN management interface is accessible from untrusted networks and the firmware is version 2.3P2T1
-
Audit access logs for unauthorized authentication attemptsReview system authentication logs, particularly those related to handheld terminal provisioning systems, for evidence of suspicious access patterns or successful authentications from unexpected sources.Affected if Firmware is 2.3P2T1 and unusual authentication activity is observed in device logs
A device is affected if it is a ZTE ZXA10 eODN unit running firmware version exactly 2.3P2T1, particularly if its management interface is network-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 dataUpdate to vendor-provided patch; reset all compromised credentials; review and restrict network access to ODN management interfaces; implement additional authentication controls such as multi-factor authentication where supported.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6877 — 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-6877 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