dbcve.org
Nip6800 FirmwareOperating system · Huawei

CVE-2020-1881

HIGH · 7.5 CVSS v3.1 Published 2020-02-28
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
NIP6800;Secospace USG6600;USG9500 products with versions of V500R001C30; V500R001C60SPC500; V500R005C00SPC100 have have a resource management error vulnerability. An attacker needs to perform specific operations to trigger a function of the affected device. Due to improper resource management of the function, the vulnerability can be exploited to cause service abnormal on affected devices.

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 a resource management error vulnerability in Huawei NIP6800, Secospace USG6600, and USG9500 firewall appliances affecting specific firmware versions (V500R001C30, V500R001C60SPC500, V500R005C00SPC100). An attacker with the ability to perform specific operations on the device can trigger a function with improper resource management, causing service abnormal (likely denial of service). The CVSS 7.5 indicates the vulnerability is network-exploitable with low attack complexity.

MitigationApply vendor-supplied firmware patches when available; if patches are unavailable, restrict access to the triggering function through access control lists and monitor for signs of resource exhaustion or service degradation.

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
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600
Usg9500 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600
Oceanstor 5310 FirmwareOperating system
Affected:= v500r007c60spc100

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 device model
    Log into the device console or check device inventory to determine if the model is Huawei NIP6800, Secospace USG6600, USG9500, or Oceanstor 5310
    Affected if Device is NOT one of these models - not affected
  2. Check firmware version on NIP6800
    Access device CLI and run command 'display version' or check firmware file name. Compare against V500R001C30
    Affected if Firmware version equals V500R001C30 - affected
  3. Check firmware version on Secospace USG6600
    Access device CLI and run command 'display version' or check firmware file name. Compare against V500R001C30SPC200 and V500R001C30SPC600
    Affected if Firmware version equals V500R001C30SPC200 or V500R001C30SPC600 - affected
  4. Check firmware version on USG9500
    Access device CLI and run command 'display version' or check firmware file name. Compare against V500R001C30SPC200 and V500R001C30SPC600
    Affected if Firmware version equals V500R001C30SPC200 or V500R001C30SPC600 - affected
  5. Check firmware version on Oceanstor 5310
    Access device management interface and check firmware version. Compare against V500R007C60SPC100
    Affected if Firmware version equals V500R007C60SPC100 - affected
  6. Monitor for service degradation
    Review system logs, performance metrics, and alert configurations for signs of resource exhaustion, unexpected service restarts, or abnormal traffic patterns that may indicate exploitation
    Affected if Device meets version criteria AND showing resource management issues - likely exploited

User is affected if their Huawei NIP6800, Secospace USG6600, USG9500, or Oceanstor 5310 device runs any of the specific firmware versions listed, and the device is network-accessible to potential attackers.

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 firmware patches when available; if patches are unavailable, restrict access to the triggering function through access control lists and monitor for signs of resource exhaustion or service degradation.

Fix this in Nip6800 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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