dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2020-9099

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 products IPS Module; NGFW Module; NIP6300; NIP6600; NIP6800; Secospace USG6300; Secospace USG6500; Secospace USG6600; USG9500 with versions of V500R001C00; V500R001C20; V500R001C30; V500R001C50; V500R001C60; V500R001C80; V500R005C00; V500R005C10; V500R005C20; V500R002C00; V500R002C10; V500R002C20; V500R002C30 have an improper authentication vulnerability. Attackers need to perform some operations to exploit the vulnerability. Successful exploit may obtain certain permissions on the device.

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

Improper authentication vulnerability in Huawei security products (IPS Module, NGFW Module, NIP6300/6600/6800, USG6300/6500/6600/9500) across multiple version ranges (V500R001 through V500R002). Attackers can perform certain operations to bypass authentication mechanisms and obtain unauthorized permissions on affected devices. The critical CVSS 9.8 score indicates trivial exploitability and complete compromise potential.

MitigationApply Huawei security patches or upgrade to fixed versions as specified in Huawei security advisory. Until patch availability, restrict network access to management interfaces and monitor for suspicious authentication patterns.

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
Ips Module FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20
Ngfw Module FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r002c00= v500r002c10= v500r002c20= v500r002c30= v500r005c00= v500r005c10= v500r005c20
Nip6300 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20
Nip6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20
Nip6800 FirmwareOperating system
Affected:= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20
Secospace Usg6300 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v500r005c00= v500r005c10= v500r005c20

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
    Run the command `display device information` or `display version` in the device CLI to retrieve the hardware model name such as NIP6300, NIP6600, NIP6800, USG6300, USG6500, USG6600, USG9500, or confirm if IPS/NGFW modules are installed.
    Affected if The device model matches one of: NIP6300, NIP6600, NIP6800, USG6300, USG6500, USG6600, USG9500, or has an IPS/NGFW module installed.
  2. Retrieve the firmware version
    Execute `display version` or `display firmware version` in the device CLI to obtain the running firmware version string.
    Affected if A firmware version is returned from the device.
  3. Compare version against affected list
    Match the obtained firmware version exactly against the following list: v500r001c00, v500r001c20, v500r001c30, v500r001c50, v500r001c60, v500r001c80, v500r002c00, v500r002c10, v500r002c20, v500r002c30, v500r005c00, v500r005c10, v500r005c20.
    Affected if The installed version exactly matches any of these version strings.
  4. Verify the specific product-version combination
    Consult the product-specific version list in the CVE advisory. Note that NIP6800 only has affected versions v500r001c60, v500r001c80, v500r005c00, v500r005c10, v500r005c20, while other models have additional affected versions.
    Affected if The installed product model and version combination appears in the affected products and versions list for this CVE.

You are affected if your Huawei security device (NIP6300/6600/6800, USG6300/6500/6600/9500, IPS Module, or NGFW Module) is running any of the specific firmware versions listed in the CVE (v500r001c00 through v500r005c20 depending on model).

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 security patches or upgrade to fixed versions as specified in Huawei security advisory. Until patch availability, restrict network access to management interfaces and monitor for suspicious authentication patterns.

Fix this in Ips Module Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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