dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2021-22312

MEDIUM · 6.5 CVSS v3.1 Published 2021-04-08
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 a memory leak vulnerability in some Huawei products. An authenticated remote attacker may exploit this vulnerability by sending specific message to the affected product. Due to not release the allocated memory properly, successful exploit may cause some service abnormal. Affected product include some versions of IPS Module, NGFW Module, 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

Memory leak vulnerability in Huawei security products (USG6300, USG6500, USG6600, USG9500, IPS Module, NGFW Module) where an authenticated remote attacker can send specific messages causing allocated memory to not be properly released, leading to service abnormalities.

MitigationApply vendor-supplied patches/updates for affected Huawei products when available. Monitor system resources and service health for signs of memory exhaustion indicating active exploitation.

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:= v500r005c00spc100= v500r005c00spc200
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:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100= v500r005c00spc200
Nip6300 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= v500r001c60spc500= v500r005c00spc100= v500r005c00spc200
Nip6600 FirmwareOperating system
Affected:= v500r001c30spc200= v500r001c30spc600= 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 product model
    Access the device console or admin web interface and locate the system information or device model display to confirm the exact model (USG6300, USG6500, USG6600, USG9500, IPS Module, NGFW Module, Nip6300, or Nip6600).
    Affected if Model is not one of these eight product lines, the device is not affected by this specific CVE.
  2. Check firmware version
    In the device admin interface, go to System > About or use the 'display version' command in the console to retrieve the installed firmware version string.
    Affected if Version matches v500r005c00spc100, v500r005c00spc200, v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500.
  3. Verify remote management is accessible
    Check if the web-based admin interface, SSL VPN, or remote management service is exposed to network access. Review firewall rules or interface bindings to determine if external IP addresses can reach the management interface.
    Affected if Remote management is enabled and reachable from untrusted networks; an attacker would need to send specifically crafted messages to trigger the memory leak.
  4. Monitor for memory exhaustion
    Use the 'display memory-usage' or 'display cpu-usage' command, or check the device health dashboard for abnormally high memory consumption that persists or grows over time.
    Affected if Memory usage is unusually high or continuously increasing without returning to baseline, which may indicate the leak is occurring.

The device is affected if it is one of the eight product models listed and runs any of the five specific firmware versions listed, with remote management exposed to allow an authenticated attacker to send the triggering messages.

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-supplied patches/updates for affected Huawei products when available. Monitor system resources and service health for signs of memory exhaustion indicating active exploitation.

Fix this in Ips Module Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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