CVE-2021-22332
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 · uneditedThere is a pointer double free vulnerability in some versions of CloudEngine 5800, CloudEngine 6800, CloudEngine 7800 and CloudEngine 12800. When a function is called, the same memory pointer is copied to two functional modules. Attackers can exploit this vulnerability by performing a malicious operation to cause the pointer double free. This may lead to module crash, compromising 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 confidenceA pointer double free vulnerability exists in Huawei CloudEngine 5800, 6800, 7800, and 12800 switches where the same memory pointer is copied to two functional modules. When attackers perform a malicious operation, it triggers a double free condition causing module crash and service disruption.
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= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800= v200r002c50spc800= v200r003c00spc810= v200r005c00spc800= v200r005c10spc800CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the CloudEngine modelRun 'display device' or 'display version' command to confirm the device is a CloudEngine 5800, 6800, 7800, or 12800 switchAffected if Device model is not one of these four models
-
Check the firmware versionRun 'display version' or check the bootrom/VRP version information. Look for version strings like v200r002c50spc800, v200r003c00spc810, v200r005c00spc800, or v200r005c10spc800Affected if Unable to retrieve firmware version or version is not visible
-
Compare installed version to affected versionsMatch your displayed firmware version exactly against the four affected version strings: v200r002c50spc800, v200r003c00spc810, v200r005c00spc800, v200r005c10spc800Affected if The installed version matches one of these four exact versions
-
Verify the vulnerability trigger conditionThis is a memory handling flaw where the same pointer is passed to two modules. Attackers trigger it via malicious operations. Check if the device is exposed to untrusted network traffic or management interfacesAffected if Device is directly accessible from untrusted networks without segmentation
You are affected if your CloudEngine 5800/6800/7800/12800 switch runs firmware version v200r002c50spc800, v200r003c00spc810, v200r005c00spc800, or v200r005c10spc800 and is exposed to potential malicious operations.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied firmware patches for affected CloudEngine models. If no patch available, implement network segmentation and access controls to limit attack surface until fix is released.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22332 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22332 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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