Cloudengine 12800 FirmwareOperating system · Huawei

CVE-2021-22393

HIGH · 7.5 CVSS v3.1 Published 2021-04-28
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 a denial of service vulnerability in some versions of CloudEngine 5800, CloudEngine 6800, CloudEngine 7800 and CloudEngine 12800. The affected product cannot deal with some messages because of module design weakness . Attackers can exploit this vulnerability by sending a large amount of specific messages to cause denial of service. This can compromise normal service.

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

A denial of service vulnerability exists in Huawei CloudEngine switch series (5800, 6800, 7800, 12800) due to a module design weakness that cannot properly handle certain specific messages. Attackers can exploit this by sending a large volume of these crafted messages to cause the affected devices to become unresponsive, disrupting normal network services.

MitigationApply vendor-supplied patches for CloudEngine devices when available. Implement network segmentation and traffic filtering to limit exposure to untrusted sources, and monitor for anomalous message patterns.

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
Cloudengine 12800 FirmwareOperating system
Affected:= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800
Cloudengine 5800Operating system
Affected:= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800
Cloudengine 6800 FirmwareOperating system
Affected:= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800
Cloudengine 7800 FirmwareOperating system
Affected:= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800

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 CloudEngine switch model
    Run 'display device' or check device labeling to confirm the model is 5800, 6800, 7800, or 12800
    Affected if Model is one of 5800, 6800, 7800, or 12800 series
  2. Check firmware version
    Run 'display version' or 'display device version' to obtain the installed firmware version
    Affected if Version matches v200r002c50spc800, v200r003c00spc810, v200r005c00spc800, or v200r005c10spc800 exactly
  3. Verify network exposure
    Check if the device management interface or network ports are reachable from untrusted networks using 'display ip interface' or reviewing ACL configurations
    Affected if Device accepts traffic from untrusted sources on ports handling the affected module messages
  4. Check device responsiveness
    Ping the device or run 'display cpu' to verify the device is responsive and not experiencing high CPU usage from message processing
    Affected if Device shows high CPU usage or is unresponsive to normal management queries

Your environment is affected if you have a CloudEngine 5800/6800/7800/12800 running any of the exact versions v200r002c50spc800, v200r003c00spc810, v200r005c00spc800, or v200r005c10spc800 and the device processes network traffic from untrusted sources.

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 for CloudEngine devices when available. Implement network segmentation and traffic filtering to limit exposure to untrusted sources, and monitor for anomalous message patterns.

Fix this in Cloudengine 12800 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-22393 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