CVE-2020-9213
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 · uneditedThere is a denial of service vulnerability in some huawei products. In specific scenarios, due to the improper handling of the packets, an attacker may craft many specific packets. Successful exploit may cause some services to be abnormal. Affected products include some versions of NGFW Module, NIP6300, NIP6600, NIP6800, Secospace USG6300, Secospace USG6500, Secospace USG6600 and SG9500.
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 confidenceDenial of service vulnerability in Huawei NGFW Module, NIP6300/6600/6800, Secospace USG6300/6500/6600, and SG9500 products. Due to improper handling of specifically crafted packets, an attacker can send malicious packets to cause service abnormalities.
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= v500r005c00= v500r001c30= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00CVSS 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 Huawei product modelLog into the device CLI or management interface and run 'display version' or check the device label/model number to confirm the exact model (NIP6300, NIP6600, NIP6800, USG6300, USG6500, USG6600, SG9500, or NGFW Module)Affected if The model matches any of: NIP6300, NIP6600, NIP6800, USG6300, USG6500, USG6600, SG9500, or NGFW Module
-
Check the installed firmware versionRun 'display version' in the device CLI or check the firmware version in the management interface. Look for version strings like v500r001c30, v500r001c60, or v500r005c00Affected if The firmware version is exactly v500r001c30, v500r001c60, or v500r005c00
-
Verify network services are exposedCheck if the device has active network interfaces and is processing traffic. Run 'display ip interface' or 'display interface' to see active interfaces and their statusAffected if The device has active network interfaces and is actively processing traffic, making it reachable to potential attackers sending malicious packets
The environment is affected if the device is a Huawei NIP6300/6600/6800, USG6300/6500/6600, SG9500, or NGFW Module running firmware version v500r001c30, v500r001c60, or v500r005c00 and has active network interfaces exposed to untrusted traffic.
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 available vendor patches or firmware updates for affected products; implement rate limiting and traffic filtering on upstream network devices as a temporary mitigation until patching is feasible.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9213 — 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-9213 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