dbcve.org
Nip6800 FirmwareOperating system · Huawei

CVE-2020-1875

MEDIUM · 5.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 →
57/100
Remediation priority · Elevated
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 versions of V500R001C30; V500R001C60SPC500; V500R005C00SPC100 have an invalid pointer access vulnerability. The software system access an invalid pointer when an abnormal condition occurs in certain operation. Successful exploit could cause certain process reboot. Affected product versions include:NIP6800 versions V500R001C30,V500R001C60SPC500;Secospace USG6600 versions V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500;USG9500 versions V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500.

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

The vulnerability exists in NIP6800, Secospace USG6600, and USG9500 products where the software accesses an invalid pointer when an abnormal condition occurs during certain operations. This invalid pointer dereference can lead to a process crash and reboot.

MitigationApply vendor-provided patches or upgrades to the affected product versions (V500R001C30, V500R001C60SPC500, V500R005C00SPC100, and SPC200/SPC600 variants). If patches are unavailable, implement network segmentation to limit exposure to the affected interfaces.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 Huawei product model
    Run the command 'display device-manufacture-info' or 'display version' on the device console to confirm the exact model is NIP6800, Secospace USG6600, or USG9500
    Affected if The product model is one of NIP6800, Secospace USG6600, or USG9500
  2. Check firmware version on NIP6800
    Run 'display version' or check the firmware file name. Look for version numbers v500r001c30 or v500r001c60spc500
    Affected if The installed version is exactly v500r001c30 or v500r001c60spc500
  3. Check firmware version on Secospace USG6600
    Run 'display version' or check the firmware file name. Look for version numbers v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500
    Affected if The installed version is exactly v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500
  4. Check firmware version on USG9500
    Run 'display version' or check the firmware file name. Look for version numbers v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500
    Affected if The installed version is exactly v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500
  5. Verify if abnormal conditions trigger process restarts
    Monitor system logs for process crash events using 'display logbuffer' or 'display ip interface' after any abnormal operations. Look for signs of unexpected process termination
    Affected if Processes crash and device reboots occur following abnormal operations on affected firmware versions

The environment is affected if the device is a NIP6800, Secospace USG6600, or USG9500 running one of the exact firmware versions listed: v500r001c30, v500r001c60spc500, v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500.

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-provided patches or upgrades to the affected product versions (V500R001C30, V500R001C60SPC500, V500R005C00SPC100, and SPC200/SPC600 variants). If patches are unavailable, implement network segmentation to limit exposure to the affected interfaces.

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-1875 — 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-1875 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