dbcve.org
Nip6300 FirmwareOperating system · Huawei

CVE-2020-9127

MEDIUM · 6.7 CVSS v3.1 Published 2020-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
Some Huawei products have a command injection vulnerability. Due to insufficient input validation, an attacker with high privilege may inject some malicious codes in some files of the affected products. Successful exploit may cause command injection.Affected product versions include:NIP6300 versions V500R001C30,V500R001C60;NIP6600 versions V500R001C30,V500R001C60;Secospace USG6300 versions V500R001C30,V500R001C60;Secospace USG6500 versions V500R001C30,V500R001C60;Secospace USG6600 versions V500R001C30,V500R001C60;USG9500 versions V500R001C30,V500R001C60.

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

Command injection vulnerability in Huawei NIP6300, NIP6600, USG6300, USG6500, USG6600, and USG9500 security products. Due to insufficient input validation, an authenticated attacker with high privileges can inject malicious commands through certain file inputs, potentially achieving arbitrary command execution on the affected device.

MitigationApply vendor-provided patches for affected versions V500R001C30 and V500R001C60, or upgrade to a patched release. Until patched, limit administrative access to trusted personnel only and monitor for anomalous command activity.

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

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

CVSS:3.1/AV:L/AC:L/PR:H/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
    Log into the device management interface or use system information commands to confirm the exact model (NIP6300, NIP6600, USG6300, USG6500, USG6600, or USG9500)
    Affected if The device is any of these six models and you are managing or auditing this device
  2. Check the installed firmware version
    Access the device CLI or web interface and retrieve the firmware version information. Compare against the affected versions v500r001c30 and v500r001c60
    Affected if The firmware version is exactly v500r001c30 or v500r001c60
  3. Verify high-privilege user access
    Review the list of accounts with administrative or high-privilege access on the device. Check whether any untrusted or unauthorized personnel have such credentials
    Affected if The device has any high-privilege accounts accessible to attackers, even if the attacker would need valid credentials
  4. Identify exposed management interfaces
    Check network configuration to determine if the device management interface (web UI or CLI) is exposed to untrusted networks rather than being isolated behind a trusted management network
    Affected if The administrative interface is reachable from untrusted networks or the internet
  5. Inspect file upload or input functionality
    Examine the device configuration for enabled file import features, particularly any features that accept files for configuration import, certificate import, or similar operations
    Affected if Any file input or import feature that accepts external files is enabled and accessible to authenticated high-privilege users

You are affected if your device is one of the six listed models AND runs firmware version v500r001c30 or v500r001c60 AND allows authenticated high-privilege users to access file input features.

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 for affected versions V500R001C30 and V500R001C60, or upgrade to a patched release. Until patched, limit administrative access to trusted personnel only and monitor for anomalous command activity.

Fix this in Nip6300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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