dbcve.org
S12700 FirmwareOperating system · Huawei

CVE-2021-22377

HIGH · 7.2 CVSS v3.1 Published 2021-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
There is a command injection vulnerability in S12700 V200R019C00SPC500, S2700 V200R019C00SPC500, S5700 V200R019C00SPC500, S6700 V200R019C00SPC500 and S7700 V200R019C00SPC500. A module does not verify specific input sufficiently. Attackers can exploit this vulnerability by sending malicious parameters to inject command. This can compromise normal service.

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 enterprise switches (S12700, S2700, S5700, S6700, S7700) V200R019C00SPC500. A module fails to properly validate input, allowing attackers to inject arbitrary commands through malicious parameters, potentially compromising the device and normal service.

MitigationApply the vendor-supplied firmware patch from Huawei for V200R019C00SPC500. If no patch is available, restrict network access to management interfaces and implement input validation controls where possible.

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
S12700 FirmwareOperating system
Affected:= v200r019c00spc500
S2700 FirmwareOperating system
Affected:= v200r019c00spc500
S5700 FirmwareOperating system
Affected:= v200r019c00spc500
S6700 FirmwareOperating system
Affected:= v200r019c00spc500
S7700 FirmwareOperating system
Affected:= v200r019c00spc500

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

CVSS:3.1/AV:N/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 switch model
    Run `display device` or `display version` command on the device console or via SNMP
    Affected if The device model is not one of S12700, S2700, S5700, S6700, or S7700 (unaffected models)
  2. Check the firmware version
    Run `display version` or `display patch-information` to obtain the exact firmware version string
    Affected if The firmware version is exactly V200R019C00SPC500 (case-sensitive match)
  3. Verify the complete version string
    Confirm the full version matches v200r019c00spc500 including the SPC500 suffix - partial version matches do not indicate this CVE
    Affected if The version string differs in any way from v200r019c00spc500 (even a single character difference means not affected)
  4. Confirm no vendor patch applied
    Run `display patch-information` to check if any patches have been installed on top of the base version
    Affected if The device runs unmodified V200R019C00SPC500 with no subsequent security patches installed

The device is affected only if it is an S12700, S2700, S5700, S6700, or S7700 switch running exactly firmware version V200R019C00SPC500 with no vendor patches applied.

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 the vendor-supplied firmware patch from Huawei for V200R019C00SPC500. If no patch is available, restrict network access to management interfaces and implement input validation controls where possible.

Fix this in S12700 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-2021-22377 — 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-2021-22377 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