CVE-2022-44560
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 · uneditedThe launcher module has an Intent redirection vulnerability. Successful exploitation of this vulnerability may cause launcher module data to be modified.
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 an Intent redirection vulnerability in an Android launcher module. Intent redirection occurs when an application improperly handles incoming intents, allowing a malicious app to redirect intents to unintended components and potentially modify launcher module data.
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.1= 12.0.0= 12.0.1= 2.0= 3.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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 device OS versionGo to Settings > About Phone on the Huawei device and locate the EMUI or HarmonyOS version number listedAffected if The version reads exactly 11.0.1, 12.0.0, 12.0.1 for EMUI, or 2.0 or 3.0.0 for HarmonyOS
-
Confirm the default launcher moduleCheck which app is set as the default home screen launcher in Settings > Apps > Default apps > Home screenAffected if A Huawei stock launcher (such as Launcher, Home, or Pocket Launcher) is set as the default and the OS version matches the affected list
-
Inspect intent filters in the launcherUse a package inspector tool (such as APK Analyzer or dumpsys) to examine the launcher APK for exported intent-filter declarations, particularly for intents with ACTION_MAIN and CATEGORY_HOMEAffected if The launcher declares exported intent filters that accept implicit intents without source validation
-
Verify intent receiver permissionsReview the launcher manifest for intent receivers and check if they have android:exported=true without android:permission checks protecting themAffected if Intent receivers are exported without permission protection, allowing any app to send intents to them
The device is affected if it runs EMUI 11.0.1, 12.0.0, or 12.0.0 or HarmonyOS 2.0 or 3.0.0 with a stock Huawei launcher set as default and the launcher has unprotected exported intent receivers that handle incoming intents.
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.
dbcve · scopedImplement proper intent handling by validating intent sources, using explicit intents where possible, and adding appropriate permission checks on intent receivers to prevent unauthorized intent redirection.
Upgrade to the latest EMUI/HarmonyOS version available for your device (EMUI 13+ or HarmonyOS 4.0+)
- 1. Go to Settings on your Huawei device
- 2. Navigate to System & Updates or General Settings
- 3. Select Software Update
- 4. Check for and install the latest available system update
- 5. After updating, verify the launcher app is updated to the latest version through the App Gallery
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44560 — 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-2022-44560 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