CVE-2021-22429
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 memory address out of bounds in smartphones. Successful exploitation of this vulnerability may cause malicious code to be executed.
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 memory address out-of-bounds vulnerability exists in smartphone firmware/components. This is a memory corruption issue that can be exploited to achieve arbitrary code execution. The critical CVSS 9.8 score indicates the vulnerability is likely remotely exploitable with low complexity and no authentication required.
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= 11.0.0= 2.0= 4.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 device manufacturerCheck if the smartphone is a Huawei device by examining the device branding, model name, or navigating to Settings > About Phone > Device nameAffected if Device is not a Huawei brand - not affected by this CVE
-
Locate OS version informationOn the Huawei phone, go to Settings > About Phone and identify which operating system is installed: EMUI, HarmonyOS, or Magic UI. The version number will be displayed under the respective OS nameAffected if Unable to determine OS type or version from About Phone menu
-
Check EMUI versionIf the phone runs EMUI, verify if the version displayed is exactly 11.0.0Affected if EMUI version equals 11.0.0 - affected by CVE-2021-22429
-
Check HarmonyOS versionIf the phone runs HarmonyOS, verify if the version displayed is exactly 2.0Affected if HarmonyOS version equals 2.0 - affected by CVE-2021-22429
-
Check Magic UI versionIf the phone runs Magic UI, verify if the version displayed is exactly 4.0.0Affected if Magic UI version equals 4.0.0 - affected by CVE-2021-22429
A Huawei smartphone running exactly EMUI 11.0.0, HarmonyOS 2.0, or Magic UI 4.0.0 is affected by this vulnerability; all other versions are not impacted based on the affected version list provided
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 security updates/patches for affected smartphone models. Until patches are available, limit device exposure to untrusted networks and avoid visiting suspicious websites or installing untrusted applications.
- Consultation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22429 — 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-22429 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