dbcve.org
Ngfw Module FirmwareOperating system · Huawei

CVE-2021-22411

MEDIUM · 6.5 CVSS v3.1 Published 2021-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 an out-of-bounds write vulnerability in some Huawei products. The code of a module have a bad judgment logic. Attackers can exploit this vulnerability by performing multiple abnormal activities to trigger the bad logic and cause out-of-bounds write. This may compromise the normal service of the module.Affected product versions include: NGFW Module versions V500R005C00SPC100,V500R005C00SPC200;Secospace USG6300 versions V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500,V500R005C00SPC100,V500R005C00SPC200;Secospace USG6500 versions V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500,V500R005C00SPC100,V500R005C00SPC200;Secospace USG6600 versions V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500,V500R005C00SPC100,V500R005C00SPC200;USG9500 versions V500R001C60SPC500,V500R005C00SPC100,V500R005C00SPC200.

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 an out-of-bounds write vulnerability in Huawei firewall products (NGFW Module, USG6300/6500/6600, USG9500) caused by flawed judgment logic in a module's code. Attackers can trigger the vulnerability by performing multiple abnormal activities that bypass input validation, causing memory corruption beyond allocated buffers. This may lead to module service compromise, potentially enabling denial of service or further exploitation.

MitigationApply Huawei vendor patches for the specific versions (V500R001C30SPC200 through V500R005C00SPC200) or restrict network access to affected devices until patching is feasible.

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
Ngfw Module FirmwareOperating system
Affected:= v500r005c00spc100= v500r005c00spc200
Secospace Usg6300 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100= v500r005c00spc200
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100= v500r005c00spc200
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100= v500r005c00spc200
Usg9500 FirmwareOperating system
Affected:= v500r001c60spc500= v500r005c00spc100= v500r005c00spc200

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

CVSS:3.1/AV:N/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 firewall model
    Check the device model via CLI command 'display device' or 'display version' or check the physical device label
    Affected if Model is NGFW Module, USG6300, USG6500, USG6600, or USG9500
  2. Retrieve the firmware version
    Execute 'display version' or 'display firmware version' in the CLI to obtain the installed firmware build
    Affected if Version matches any of: v500r001c30spc200, v500r001c30spc600, v500r001c60spc500, v500r005c00spc100, v500r005c00spc200
  3. Confirm the vulnerable module is active
    Check for active NGFW module or security policy module status via 'display module-information' or 'display current-configuration' looking for NGFW/IPS/IPS module entries
    Affected if The NGFW or related security inspection module is loaded and active on the device
  4. Verify abnormal activity handling configuration
    Review input validation or traffic anomaly detection settings using 'display current-configuration | include abnormal' or check IPS/attack defense logs
    Affected if Abnormal activity detection or input validation bypass conditions can be triggered

A user is affected if their device is an NGFW Module, USG6300, USG6500, USG6600, or USG9500 running any of the firmware versions v500r001c30spc200 through v500r005c00spc200 with the NGFW or security inspection module enabled.

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 vendor patches for the specific versions (V500R001C30SPC200 through V500R005C00SPC200) or restrict network access to affected devices until patching is feasible.

Fix this in Ngfw 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-2021-22411 — 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-22411 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