CVE-2021-22389
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 Permission Control Vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may cause certain codes 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 confidenceThis is a permission control vulnerability in Huawei smartphones that allows attackers to bypass normal permission checks and execute arbitrary code. The CVSS 9.8 score indicates the vulnerability is exploitable remotely without authentication and can lead to complete system compromise.
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= 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 your Huawei device software versionGo to Settings > About Phone on your Huawei or Honor smartphone. Look for the version field that displays either EMUI or Magic UI version number.Affected if The displayed version is exactly 11.0.0 for EMUI or exactly 4.0.0 for Magic UI.
-
Confirm the Android version for contextIn the same About Phone section, note the Android version displayed. This helps identify the broader software environment.Affected if Running Android 10 or Android 11 in combination with the affected EMUI/Magic UI versions.
-
Check if device is receiving vendor updatesGo to Settings > System > Software Update. Check if any pending updates exist or if the device shows it is up to date.Affected if The device shows no available updates while running the affected versions, indicating it may be unpatched.
-
Inventory device modelIn Settings > About Phone, note the model number (such as P30, Mate 30, or Honor models). Cross-reference with Huawei's security advisory for CVE-2021-22389.Affected if The device model is confirmed to run EMUI 11.0.0 or Magic UI 4.0.0 and is not listed as patched in Huawei's security bulletin.
You are affected if your Huawei or Honor smartphone runs exactly EMUI 11.0.0 or Magic UI 4.0.0 and has not received the vendor security patch addressing CVE-2021-22389.
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 and firmware patches from Huawei for affected smartphone models. Organizations should inventory all Huawei devices and ensure they receive the latest security patches.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22389 — 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-22389 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