CVE-2021-22336
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 an Improper Control of Generation of Code vulnerability in Huawei Smartphone. Successful exploitation of this vulnerability may cause denial of security services on a rooted device.
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 confidenceThis is a code injection vulnerability (CWE-94) in Huawei smartphones where improper control of code generation allows attackers to inject malicious code. The CVSS 7.5 score indicates high exploitability. The description notes exploitation may cause denial of security services on rooted devices, suggesting the vulnerability can bypass or disable security mechanisms.
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.0.0= 10.1.0= 10.1.1= 11.0.0= 3.0.0= 3.1.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
- 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.
-
Check the EMUI or Magic UI version installed on the deviceNavigate to Settings > About Phone > Version on the Huawei device. Alternatively, go to Settings > System > About Phone to view the EMUI/Magic UI version and build number.Affected if The displayed version exactly matches 10.0.0, 10.1.0, 10.1.1, or 11.0.0 for EMUI, or 3.0.0, 3.1.0, 3.1.1, or 4.0.0 for Magic UI.
-
Determine if the device has been rootedUse a root checker application from a trusted source, or manually verify by checking for the presence of the su binary in /system/bin/ or /system/xbin/, or look for Superuser/SuperSU apps in the application list.Affected if The device has root access enabled or root binaries are present on the system.
-
Verify if installation from unknown sources is permittedGo to Settings > Security & Privacy > Device Administration (or Settings > Apps > Menu > Special Access > Install unknown apps) and check which apps are allowed to install other applications.Affected if Applications from unknown or untrusted sources are permitted to install other apps.
-
Review installed applications for suspicious or untrusted appsNavigate to Settings > Apps > Downloaded to review all installed applications. Look for apps from unknown developers or applications that were not installed from the official Huawei AppGallery.Affected if Applications from untrusted or unknown sources are installed on the device.
A user is affected if their device runs exactly version 10.0.0, 10.1.0, 10.1.1, or 11.0.0 (EMUI) or 3.0.0, 3.1.0, 3.1.1, or 4.0.0 (Magic UI) AND the device is rooted or has applications from untrusted sources installed.
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/security updates from Huawei. Until a patch is available, restrict device rooting and limit installation of applications from untrusted sources. Monitor Huawei's security advisory for affected models and patch release.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22336 — 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-22336 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