dbcve.org
Nip6800 FirmwareOperating system · Huawei

CVE-2020-1815

HIGH · 7.5 CVSS v3.1 Published 2020-02-18
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 NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00 have a memory leak vulnerability. The software does not sufficiently track and release allocated memory while parse certain message, the attacker sends the message continuously that could consume remaining memory. Successful exploit could cause memory exhaust.

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 confidence

Memory leak vulnerability in Huawei NIP6800 and USG6600/USG9500 security appliances. The devices fail to properly release allocated memory when parsing certain messages, allowing an unauthenticated remote attacker to continuously send crafted messages that exhaust available memory, causing denial of service.

MitigationApply Huawei vendor patches for the specific affected firmware versions (V500R001C30, V500R001C60SPC500, V500R005C00, V500R001C30SPC200, V500R001C30SPC600). If patches are unavailable, implement network-level rate limiting and traffic filtering to restrict continuous message attacks.

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
Nip6800 FirmwareOperating system
Affected:= v500r001c30= v500r001c60spc500= v500r005c00
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00
Usg9500 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= 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
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 checks

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

  1. Identify the device model
    Check the product model of the Huawei security appliance. Look for NIP6800, USG6600, or USG9500 in the device management interface, CLI output (display device), or system information page.
    Affected if The device is not one of these three models (NIP6800, USG6600, USG9500)
  2. Check firmware version on NIP6800
    For NIP6800 devices, access the device CLI and run 'display version' or check the firmware version through the web management interface under System > Device Information.
    Affected if The firmware version is exactly v500r001c30, v500r001c60spc500, or v500r005c00
  3. Check firmware version on USG6600
    For USG6600 devices, access the device CLI and run 'display version' or check the firmware version through the web management interface under System > Device Information.
    Affected if The firmware version is exactly v500r001c30spc200, v500r001c30spc600, v500r001c60spc500, or v500r005c00
  4. Check firmware version on USG9500
    For USG9500 devices, access the device CLI and run 'display version' or check the firmware version through the web management interface under System > Device Information.
    Affected if The firmware version is exactly v500r001c30spc200, v500r001c30spc600, v500r001c60spc500, or v500r005c00
  5. Verify message parsing features are enabled
    Confirm that the device has message parsing features active. Check if the device is configured to process external messages on any interface, typically found in Security Policy or Attack Defense settings.
    Affected if Message parsing features are enabled and the device processes external network traffic
  6. Confirm device is network accessible
    Verify that the device has reachable network interfaces exposed to the network where potential attackers could send crafted messages.
    Affected if The device has externally accessible management or data interfaces

A user is affected if they have a Huawei NIP6800, USG6600, or USG9500 appliance running any of the specific firmware versions listed, with message parsing enabled and network accessibility.

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 Huawei vendor patches for the specific affected firmware versions (V500R001C30, V500R001C60SPC500, V500R005C00, V500R001C30SPC200, V500R001C30SPC600). If patches are unavailable, implement network-level rate limiting and traffic filtering to restrict continuous message attacks.

Fix this in Nip6800 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1815 — 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-1815 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