dbcve.org
AndroidOperating system · Google

CVE-2022-20426

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
In multiple functions of many files, there is a possible obstruction of the user's ability to select a phone account due to resource exhaustion. 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-236263294

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 confidence

A local denial of service vulnerability in Android's phone account selection functionality allows an attacker to cause resource exhaustion, preventing users from selecting phone accounts. The issue exists in multiple functions across many files, requiring substantial code changes to remediate.

MitigationApply the Android security patch for CVE-2022-20426. The vulnerability is addressed through platform-level code changes that properly manage resources to prevent exhaustion during phone account selection.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.0= 12.1= 13.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The displayed version is 10.0, 11.0, 12.0, 12.1, or 13.0 exactly (not a later security patch version)
  2. Verify phone calling capability exists
    Check if the device has Phone app functionality: look for Phone or Calls in Settings > Apps, or run 'pm list packages | grep -i phone' via ADB
    Affected if A Phone or Dialer app is installed and functional on the device
  3. Confirm phone account selection feature is present
    Open the Phone app, access Settings within Phone app, look for 'Calls > Calling accounts' or 'Calls > Phone accounts' settings, or check for 'android.accounts.TYPE_IM' account type availability
    Affected if The device shows phone account selection or calling account options in Phone settings

The device is affected if it runs Android 10.0, 11.0, 12.0, 12.1, or 13.0 AND includes phone account selection functionality that could be exploited to cause resource exhaustion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch for CVE-2022-20426. The vulnerability is addressed through platform-level code changes that properly manage resources to prevent exhaustion during phone account selection.

Recommended fix High confidence

Android 13 or later / December 2022 security patch level or later

  1. 1. Verify the current Android version on the affected device by navigating to Settings > About Phone > Android version
  2. 2. Check the current security patch level by going to Settings > About Phone > Security patch level
  3. 3. Upgrade the device to Android 13 or later which contains the fix for this vulnerability
  4. 4. Alternatively, apply the monthly security update that addresses CVE-2022-20426 (check Android Security Bulletin from late 2022)
  5. 5. After upgrade, verify the security patch level includes the fix by checking Settings > About Phone > Security patch level
Caveat Upgrading Android version may affect app compatibility; ensure critical apps are compatible before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20426 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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