CVE-2020-6873
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 has a DoS vulnerability. Because the equipment couldn’t distinguish the attack packets and normal packets with valid http links, the remote attackers could use this vulnerability to cause the equipment WEB/TELNET module denial of service and make the equipment be out of management. This affects: ZXR10 2800-4_ALMPUFB(LOW), all versions up to V3.00.40.
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 ZXR10 2800-4 devices have a DoS vulnerability where the equipment cannot distinguish attack packets from legitimate HTTP traffic. Remote attackers can send specially crafted packets to cause the WEB/TELNET module to fail, rendering the device unmanageable.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 device via console, SSH, or web interface and retrieve the hardware model information. Look for 'ZXR10 2800-4' in the device information or system status.Affected if The device is not a ZTE ZXR10 2800-4 model, then it is not affected by this specific CVE.
-
Determine the firmware versionAccess the device via console, SSH, or web interface and retrieve the firmware/software version. Check the version number against the affected range.Affected if The firmware version is greater than 3.00.40, then it is not affected by this CVE.
-
Check if WEB/TELNET module is enabled and accessibleInspect the device configuration to determine if the WEB management interface or TELNET service is enabled. Verify if these services are bound to any accessible network interface.Affected if The WEB/TELNET module is disabled or not accessible from the network, then the device cannot be exploited via this vulnerability.
-
Assess network exposure of management interfacesReview access control lists, firewall rules, or interface bindings to determine if the WEB/TELNET management ports are exposed to untrusted networks or the public internet.Affected if The WEB/TELNET management interfaces are accessible from untrusted networks, the device is vulnerable to remote attack.
The device is affected if it is a ZTE ZXR10 2800-4 with firmware version 3.00.40 or lower, and the WEB/TELNET management module is enabled and accessible from the network where attackers could send malicious packets.
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 dataUpgrade ZTE ZXR10 2800-4 firmware to a version beyond V3.00.40 if available. Until then, restrict WEB/TELNET access to trusted networks via firewall rules or ACLs to reduce attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6873 — 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-6873 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