CVE-2022-20414
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 · uneditedIn setImpl of AlarmManagerService.java, there is a possible way to put a device into a boot loop due to an uncaught exception. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-234441463
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 confidenceIn the setImpl method of AlarmManagerService.java, an uncaught exception can propagate up and cause the system to crash repeatedly, resulting in a boot loop. This local denial of service requires no additional execution privileges or user interaction to exploit on affected Android devices.
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= 11.0= 12.0= 12.1= 13.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Android OS versionOpen Settings > About Phone > Android version, or run `adb shell getprop ro.build.version.release` via ADBAffected if The version shown is 10.0, 11.0, 12.0, 12.1, or 13.0 exactly
-
Check Android SDK versionRun `adb shell getprop ro.build.version.sdk` via ADB or check in Settings > About Phone > Build NumberAffected if The SDK version returned is 29, 30, 31, 32, or 33 corresponding to Android 10-13 respectively
-
Verify AlarmManagerService availabilityThe AlarmManagerService is a core system service; verify it exists by checking /system/framework/services.jar or by confirming AlarmManager functionality works via `adb shell dumpsys alarm`Affected if The service is present and functional, which is the default state on affected Android versions
A device is likely affected if it runs Android 10.0, 11.0, 12.0, 12.1, or 13.0 and has not received the October 2022 or later Android security patch update.
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 · scopedThis vulnerability is addressed through monthly security updates from Android device OEMs. Organizations should ensure all managed Android devices are enrolled in and receiving regular security patch updates.
Android 12L or Android 13
- Verify the current Android version on the device via Settings > About Phone > Android version
- Check if a software update is available via Settings > System > Software Update or Settings > About Phone > Software Update
- If update is available, download and install the latest available update
- Ensure the device is charging and connected to Wi-Fi during the update process
- After updating, verify the device is running Android 12L or Android 13 by checking Settings > About Phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20414 — 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-20414 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