CVE-2020-1858
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 · uneditedHuawei products NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00SPC100; Secospace USG6600 versions V500R001C30SPC600, V500R001C60SPC500, and V500R005C00SPC100; and USG9500 versions V500R001C30SPC600, V500R001C60SPC500, and V500R005C00SPC100 have a denial of service vulnerability. Attackers need to perform a series of operations in a special scenario to exploit this vulnerability. Successful exploit may cause the new connections can't be established, result in a denial of service.
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 a denial of service vulnerability in Huawei NIP6800, USG6600, and USG9500 security appliances. Successful exploitation prevents new connections from being established, effectively blocking legitimate traffic. The attack requires a specific series of operations in a particular scenario, suggesting it may involve malformed packets or specific connection states.
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 device modelLog into the device CLI or management interface and run 'display device' or check the hardware label to confirm the model is one of: NIP6800, USG6600, or USG9500Affected if The device model is not NIP6800, USG6600, or USG9500 (other models are not affected by this CVE)
-
Check the firmware versionRun 'display version' in the device CLI or check the firmware version in the management interfaceAffected if The firmware version matches one of: v500r001c30, v500r001c30spc200, v500r001c30spc600, v500r001c60spc500, v500r005c00spc100
-
Confirm the device is processing trafficRun 'display ip interface brief' or 'display zone' to verify that interfaces are configured and active, and check that the device is not in bypass modeAffected if The device is actively processing network traffic (the vulnerability affects new connection establishment)
-
Verify if the vulnerability trigger scenario is possibleReview the security policy configuration with 'display security-policy all' to check if the device accepts connections from untrusted networks (the CVE mentions a specific scenario involving malformed packets or specific connection states)Affected if Security policies allow traffic from untrusted sources to reach the device without proper filtering
The device is affected if it is a NIP6800, USG6600, or USG9500 running one of the listed firmware versions and is actively processing traffic from potentially untrusted networks.
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 patches or firmware updates from Huawei for the affected versions. As a defense-in-depth measure, implement connection rate limiting and consider network segmentation to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1858 — 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-1858 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