dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2021-22356

MEDIUM · 5.9 CVSS v3.1 Published 2021-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 weak secure algorithm vulnerability in Huawei products. A weak secure algorithm is used in a module. Attackers can exploit this vulnerability by capturing and analyzing the messages between devices to obtain information. This can lead to information leak.Affected product versions include: IPS Module V500R005C00SPC100, V500R005C00SPC200; NGFW Module V500R005C00SPC100, V500R005C00SPC200; Secospace USG6300 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; Secospace USG6500 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; Secospace USG6600 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; USG9500 V500R001C30SPC200, V500R001C30SPC600, 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 · high confidence

This vulnerability involves the use of weak secure algorithms (likely weak cipher suites, deprecated protocols like TLS 1.0/1.1, or weak cryptographic parameters) in Huawei IPS, NGFW, and USG security products. Attackers can perform man-in-the-middle attacks by capturing and analyzing network traffic between devices to obtain sensitive information through the weak cryptographic protection.

MitigationDisable weak cryptographic algorithms and protocols (e.g., TLS 1.0/1.1, weak cipher suites, MD5/SHA1 for certain purposes) and configure only strong algorithms (TLS 1.2+, AES-256, strong key lengths). Apply vendor patches for affected versions where available.

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

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

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

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 installed firmware version
    Log into the device console and run the version display command (for example, `display version` or `display device version`) to retrieve the current firmware version
    Affected if The installed version matches one of the affected versions: v500r005c00spc100, v500r005c00spc200, v500r001c30spc200, v500r001c30spc600, or v500r001c60spc500
  2. Locate SSL/TLS protocol configuration
    Access the device configuration mode and navigate to the SSL/TLS or encryption settings area. Look for protocol version settings (commonly found under SSL policy, protocol configuration, or security profile settings)
    Affected if TLS version 1.0 or TLS version 1.1 is enabled or allowed on the device
  3. Review cipher suite configuration
    Examine the cipher suite list configured on the device. Check for weak or deprecated cipher configurations (often found in SSL policy, cipher list, or encryption algorithm settings)
    Affected if Weak cipher suites such as those using MD5, SHA-1 (for certain purposes), 3DES, RC4, or short key lengths (less than 128-bit) are enabled or preferred
  4. Verify VPN or tunnel encryption settings
    Inspect VPN configuration sections (IPSec, SSL VPN, or site-to-site tunnels) for the cryptographic algorithms in use. Check the proposal or transform set settings
    Affected if Weak algorithms are selected in VPN or tunnel encryption settings, allowing weak cryptographic protection for network traffic

A device is affected if it runs one of the listed firmware versions AND has weak cryptographic algorithms (TLS 1.0/1.1 or weak cipher suites) enabled in its configuration.

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

Disable weak cryptographic algorithms and protocols (e.g., TLS 1.0/1.1, weak cipher suites, MD5/SHA1 for certain purposes) and configure only strong algorithms (TLS 1.2+, AES-256, strong key lengths). Apply vendor patches for affected versions where available.

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