CVE-2020-1863
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 USG6000V with versions V500R001C20SPC300, V500R003C00SPC100, and V500R005C00SPC100 have an out-of-bounds read vulnerability. Due to a logical flaw in a JSON parsing routine, a remote, unauthenticated attacker could exploit this vulnerability to disrupt service in the affected products.
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 · high confidenceHuawei USG6000V firewall products contain an out-of-bounds read vulnerability in their JSON parsing routine. A logical flaw allows remote, unauthenticated attackers to trigger the vulnerability via specially crafted JSON input, leading to service disruption (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= v500r001c20spc300= v500r003c00spc100= 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.
-
Confirm device model is USG6000VLog into the firewall CLI and run 'display device' or 'show system-info' to verify the hardware model is USG6000VAffected if Device model is not USG6000V (different models are not affected by this specific CVE)
-
Check installed firmware versionRun 'display version' or 'show version' in the CLI to retrieve the current firmware version stringAffected if Version matches v500r001c20spc300, v500r003c00spc100, or v500r005c00spc100 exactly
-
Verify JSON parsing interface is accessibleCheck if the device management interface (Web UI/REST API) is enabled and reachable from network segments. Run 'display http server' and 'display https server' to see if web management is enabled, then review the bind address configurationAffected if HTTP/HTTPS management is enabled and bound to an IP address accessible from untrusted networks (enables remote attack vector)
-
Review firewall policy for JSON service exposureRun 'display security-policy all' or check the security policy configuration to see if traffic to the device management interface (typically ports 443, 8443) from external/untrusted zones is permittedAffected if Security policy allows traffic from untrusted zones to the management interface, permitting unauthenticated JSON input to reach the device
A user is affected if they are running one of the three specific firmware versions AND the device management interface is reachable from untrusted networks, allowing unauthenticated attackers to send malicious JSON requests.
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 Huawei firmware patches for the affected versions (V500R001C20SPC300, V500R003C00SPC100, V500R005C00SPC100) or upgrade to a patched version. If immediate patching is not feasible, consider network segmentation to limit exposure to untrusted inputs.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1863 — 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-1863 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