CVE-2020-1873
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 · uneditedNIP6800;Secospace USG6600;USG9500 products with versions of V500R001C30; V500R001C60SPC500; V500R005C00SPC100 have an out-of-bounds read vulnerability. An unauthenticated attacker crafts malformed message with specific parameter and sends the message to the affected products. Due to insufficient validation of message, which may be exploited to cause the device reboot.
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 out-of-bounds read vulnerability in Huawei NIP6800, Secospace USG6600, and USG9500 security appliances due to insufficient validation of malformed messages. An unauthenticated attacker can send specially crafted messages with specific parameters to trigger the vulnerability, causing device reboot (denial of service).
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= v500r001c30= v500r001c60spc500= v500r005c00spc100= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 appliance modelLog into the device management interface or check the physical device label to determine if the model is Huawei NIP6800, Secospace USG6600, or USG9500Affected if The model is not one of these three, the device is not affected by this CVE
-
Determine the firmware versionAccess the device CLI or web management interface and run the command to display the firmware version, typically 'display version' in CLI or check the system information page in web UIAffected if The installed firmware version matches or falls within the affected version ranges (v500r001c30, v500r001c30spc200, v500r001c30spc600, v500r001c60spc500, v500r005c00spc100)
-
Check for unexpected device rebootsReview system logs for sudden restarts or crash dumps using 'display logbuffer' or checking the logging subsystem for timestamps indicating unexpected rebootsAffected if The device has experienced unexplained reboots or crash events that correlate with the timeframe since the vulnerability was disclosed (2020)
-
Verify network exposureCheck the device network configuration to determine if it is directly accessible from untrusted networks on any management or service interfacesAffected if The device management interface is exposed to the internet or untrusted networks without proper filtering
The environment is affected if the device model is NIP6800, USG6600, or USG9500 AND the installed firmware version matches one of the affected versions listed in the CVE.
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 dataApply vendor-supplied firmware patches for versions V500R001C30, V500R001C60SPC500, and V500R005C00SPC100. If patches are unavailable, implement network-level filtering to block malformed messages targeting the affected service.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.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 $5,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1873 — 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-1873 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