dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2021-37129

HIGH · 7.5 CVSS v3.1 Published 2021-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 an out of bounds write vulnerability in some Huawei products. The vulnerability is caused by a function of a module that does not properly verify input parameter. Successful exploit could cause out of bounds write leading to a denial of service condition.Affected product versions include:IPS Module V500R005C00,V500R005C20;NGFW Module V500R005C00;NIP6600 V500R005C00,V500R005C20;S12700 V200R010C00SPC600,V200R011C10SPC500,V200R011C10SPC600,V200R013C00SPC500,V200R019C00SPC200,V200R019C00SPC500,V200R019C10SPC200,V200R020C00,V200R020C10;S1700 V200R010C00SPC600,V200R011C10SPC500,V200R011C10SPC600;S2700 V200R010C00SPC600,V200R011C10SPC500,V200R011C10SPC600;S5700 V200R010C00SPC600,V200R010C00SPC700,V200R011C10SPC500,V200R011C10SPC600,V200R019C00SPC500;S6700 V200R010C00SPC600,V200R011C10SPC500,V200R011C10SPC600;S7700 V200R010C00SPC600,V200R010C00SPC700,V200R011C10SPC500,V200R011C10SPC600;S9700 V200R010C00SPC600,V200R011C10SPC500,V200R011C10SPC600;USG9500 V500R005C00,V500R005C20.

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

An out-of-bounds write vulnerability exists in certain Huawei network product modules due to improper input parameter validation. The flaw allows an attacker to write data beyond allocated memory boundaries, potentially causing a denial of service condition. The vulnerability is network-exploitable with CVSS 7.5 indicating high severity.

MitigationApply vendor-supplied firmware updates for the affected product versions. If patches are unavailable, implement network segmentation to limit exposure and monitor vendor security advisories for updates.

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:= v500r005c00= v500r005c20
Ngfw Module FirmwareOperating system
Affected:= v500r005c00
Nip6600 FirmwareOperating system
Affected:= v500r005c00= v500r005c20
S12700 FirmwareOperating system
Affected:= v200r010c00spc600= v200r011c10spc500= v200r011c10spc600= v200r013c00spc500= v200r019c00spc200= v200r019c00spc500= v200r019c10spc200= v200r020c00= v200r020c10
S1700 FirmwareOperating system
Affected:= v200r010c00spc600= v200r011c10spc500= v200r011c10spc600
S2700 FirmwareOperating system
Affected:= v200r010c00spc600= v200r011c10spc500= v200r011c10spc600
S5700 FirmwareOperating system
Affected:= v200r010c00spc600= v200r010c00spc700= v200r011c10spc500= v200r011c10spc600= v200r019c00spc500
S6700 FirmwareOperating system
Affected:= v200r010c00spc600= v200r011c10spc500= v200r011c10spc600

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
High

CVSS:3.1/AV:N/AC:L/PR:N/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 device model
    Use command 'display device' or check the physical device label to determine if the device is one of: Ips Module, Ngfw Module, Nip6600, S12700, S1700, S2700, S5700, or S6700
    Affected if The device model matches any of these product lines
  2. Check the firmware version on Ips Module, Ngfw Module, or Nip6600
    Use command 'display version' or access the module management interface to retrieve the firmware version
    Affected if The version is exactly v500r005c00 or v500r005c20
  3. Check the firmware version on S12700, S1700, S2700, S5700, or S6700
    Use command 'display version' on the device CLI to retrieve the firmware version
    Affected if The version exactly matches one of: v200r010c00spc600, v200r011c10spc500, v200r011c10spc600, v200r013c00spc500, v200r019c00spc200, v200r019c00spc500, v200r019c10spc200, v200r020c00, v200r020c10, or v200r010c00spc700 (for S5700 only)
  4. Verify the affected module or feature is active
    Check if the Ips Module, Ngfw Module, or network processing module is loaded and running using 'display module' or 'display current-configuration' commands
    Affected if The vulnerable module is installed and actively processing network traffic

The environment is affected if the device is one of the listed models AND the installed firmware version exactly matches one of the versions specified in the affected versions list.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates for the affected product versions. If patches are unavailable, implement network segmentation to limit exposure and monitor vendor security advisories for updates.

Recommended fix Moderate confidence

Upgrade to the next available firmware version beyond those listed in the affected versions (e.g., V200R019C10SPC500 or later for S12700; V200R011C10SPC600 or later for S1700/S2700/S5700/S6700). Specific fixed versions should be confirmed from Huawei's official security advisory.

  1. 1. Identify the exact model and current firmware version of the Huawei device using the command 'display version' or via the management interface.
  2. 2. Access Huawei's official security advisory page at www.huawei.com to locate the specific patch or firmware version that addresses CVE-2021-37129.
  3. 3. Download the recommended fixed firmware version from Huawei's official support portal (support.huawei.com).
  4. 4. Before applying the upgrade, back up the current device configuration using 'display current-configuration' or through the web management interface.
  5. 5. Upload the new firmware to the device via FTP, TFTP, or USB, depending on device capabilities.
  6. 6. Execute the firmware upgrade command or use the web interface to initiate the upgrade process.
  7. 7. After the upgrade completes, verify the new firmware version using 'display version'.
  8. 8. Confirm the configuration is intact and test device functionality to ensure normal operation.
Caveat Review Huawei's release notes for the target firmware version to check for configuration changes or feature modifications that may affect existing network setup.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ips Module 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-37129 — 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-37129 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