CVE-2021-22348
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 Buffer Improper Operation Limit Vulnerability in Huawei Smartphone. Successful exploitation of this vulnerability may cause code to execute.
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 buffer improper operation limit vulnerability in Huawei smartphones allows remote attackers to execute arbitrary code, likely due to insufficient bounds checking when processing memory operations. The critical CVSS 9.8 score indicates network-exploitable code execution without authentication or user interaction.
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= 10.1.1= 11.0.0= 3.1.1= 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.
-
Confirm Huawei smartphone in useVerify the device is a Huawei smartphone running EMUI or Magic UI operating system. Check device model and manufacturer in Settings > About Phone.Affected if Device is not a Huawei smartphone running EMUI or Magic UI (not affected)
-
Check EMUI version numberOn the Huawei device, go to Settings > About Phone > Version. Note the EMUI version number displayed (typically shown as EMUI X.X.X).Affected if EMUI version is exactly 10.1.1 or 11.0.0 (vulnerable)
-
Check Magic UI version numberOn the Huawei device, go to Settings > About Phone > Version. Note the Magic UI version number displayed (typically shown as Magic UI X.X.X).Affected if Magic UI version is exactly 3.1.1 or 4.0.0 (vulnerable)
-
Verify version match against CVE listCompare the installed EMUI or Magic UI version to the affected list: EMUI 10.1.1, EMUI 11.0.0, Magic UI 3.1.1, or Magic UI 4.0.0. Exact version match is required.Affected if Installed version exactly matches one of: 10.1.1, 11.0.0, 3.1.1, or 4.0.0
The environment is affected only if the Huawei smartphone is running exactly EMUI 10.1.1, EMUI 11.0.0, Magic UI 3.1.1, or Magic UI 4.0.0; other versions are not vulnerable to this specific CVE.
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 available Huawei firmware updates for affected smartphone models; until patches are available, minimize exposure by avoiding untrusted network connections and unverified applications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22348 — 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-22348 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