dbcve.org
Ngfw Module FirmwareOperating system · Huawei

CVE-2020-1856

HIGH · 7.5 CVSS v3.1 Published 2020-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Huawei NGFW Module, NIP6300, NIP6600, Secospace USG6500, Secospace USG6600, and USG9500 versions V500R001C30, V500R001C60, and V500R005C00 have an information leakage vulnerability. An attacker can exploit this vulnerability by sending specific request packets to affected devices. Successful exploit may lead to information leakage.

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 confidence

This is an information leakage vulnerability in Huawei NGFW and USG series security appliances. An unauthenticated remote attacker can send specific request packets to affected devices to trigger the vulnerability, potentially exposing sensitive information such as configuration data, credentials, or session information.

MitigationApply vendor-supplied patches for versions V500R001C30, V500R001C60, and V500R005C00. As an interim measure, restrict network access to the device management interfaces using ACLs or firewall rules to limit exposure to trusted IP addresses only.

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
Ngfw Module FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Nip6300 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Nip6600 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Usg9500 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device management console or check the physical device label to determine the exact model (e.g., NGFW Module, Nip6300, Nip6600, Secospace Usg6500, Secospace Usg6600, or Usg9500)
    Affected if The device is any of the Huawei NGFW or USG series models listed in the affected products
  2. Check the firmware version
    Log into the device CLI or web management interface and run the command to display the firmware version, typically 'display version' in CLI or checking the system information page in web UI
    Affected if The running firmware version is exactly v500r001c30, v500r001c60, or v500r005c00
  3. Verify network exposure of management interface
    Review firewall rules, ACLs, or interface configurations to determine if the device management interface (web UI port 443/80, SSH port 22) is accessible from untrusted networks or the internet
    Affected if Management interfaces are reachable from untrusted IP addresses or the public internet without ACL restrictions
  4. Check for suspicious access logs
    Review authentication logs, audit logs, and access logs for repeated unauthenticated requests to specific endpoints or unusual patterns that may indicate exploitation attempts
    Affected if Logs show unauthenticated requests to specific URLs or endpoints that could indicate attempts to trigger the information leakage

The environment is affected if the device is a Huawei NGFW, Nip, or USG series model running firmware version v500r001c30, v500r001c60, or v500r005c00 and its management interface is exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for versions V500R001C30, V500R001C60, and V500R005C00. As an interim measure, restrict network access to the device management interfaces using ACLs or firewall rules to limit exposure to trusted IP addresses only.

Fix this in Ngfw Module Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1856 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-1856 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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