dbcve.org
Nip6300 FirmwareOperating system · Huawei

CVE-2021-22321

MEDIUM · 5.3 CVSS v3.1 Published 2021-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
There is a use-after-free vulnerability in a Huawei product. A module cannot deal with specific operations in special scenarios. Attackers can exploit this vulnerability by performing malicious operations. This can cause memory use-after-free, compromising normal service. Affected product include some versions of NIP6300, NIP6600, NIP6800, S1700, S2700, S5700, S6700 , S7700, S9700, Secospace USG6300, Secospace USG6500, Secospace USG6600 and USG9500.

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

Use-after-free vulnerability in a Huawei product module that fails to properly handle specific operations in special scenarios. Attackers can exploit this through malicious operations to cause memory use-after-free, compromising normal service functionality.

MitigationApply vendor-provided patches for affected products when available; until then, restrict network access to vulnerable devices and monitor for anomalous activity that could indicate exploitation attempts.

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
Nip6800 FirmwareOperating system
Affected:= v500r001c60
S12700 FirmwareOperating system
Affected:= v200r007c01= v200r007c01b102= v200r008c00= v200r010c00= v200r010c00spc300= v200r011c00= v200r011c00spc100= v200r011c10
S1700 FirmwareOperating system
Affected:= v200r009c00spc200= v200r009c00spc500= v200r010c00= v200r010c00spc300= v200r011c00= v200r011c00spc100= v200r011c10
S2700 FirmwareOperating system
Affected:= v200r008c00= v200r010c00= v200r010c00spc300= v200r011c00= v200r011c00spc100= v200r011c10
S5700 FirmwareOperating system
Affected:= v200r008c00= v200r010c00= v200r010c00spc300= v200r011c00= v200r011c00spc100= v200r011c10= v200r011c10spc100
S6700 FirmwareOperating system
Affected:= v200r008c00= v200r010c00= v200r010c00spc300= v200r011c00= v200r011c00spc100= v200r011c10= v200r011c10spc100

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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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
    Log into the device CLI and run 'display device' or 'display version' to confirm the model number (Nip6300, Nip6600, Nip6800, S12700, S1700, S2700, S5700, or S6700)
    Affected if The model is one of the affected products listed in the CVE
  2. Check the installed firmware version
    Run 'display version' in the device CLI to obtain the current firmware version string
    Affected if The firmware version matches any of the specific versions listed for your model (for example: Nip6300 v500r001c30 or v500r001c60; S5700 v200r011c10spc100, etc.)
  3. Verify the vulnerable module is active
    Run 'display module' or 'display current-configuration | include [module_name]' to check if the affected security module is loaded and running
    Affected if The module that contains the use-after-free vulnerability is enabled and processing traffic
  4. Check for network exposure
    Run 'display ip interface' or 'display interface' to list all active network interfaces and their IP addresses
    Affected if The device has management or service interfaces directly accessible from untrusted networks (not behind a firewall or ACL)

You are affected if your device model and firmware version exactly match one of the versions listed in the CVE and the vulnerable module is actively running.

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 products when available; until then, restrict network access to vulnerable devices and monitor for anomalous activity that could indicate exploitation attempts.

Fix this in Nip6300 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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