dbcve.org
AndroidOperating system · Google

CVE-2022-20451

HIGH · 7.8 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 →
81/100
Remediation priority · High
No privileges

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 onCallRedirectionComplete of CallsManager.java, there is a possible permissions bypass due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-235098883

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 · high confidence

A missing permission check in the onCallRedirectionComplete method of CallsManager.java in Android allows a local attacker to bypass permission requirements and escalate privileges without additional execution privileges, though user interaction is required for exploitation.

MitigationApply Android security updates for affected versions (Android-10 through Android-13) as they become available from device OEMs; this is a platform-level vulnerability requiring a system patch from Google.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Check Android OS version
    Go to Settings > About Phone > Android version and note the displayed version number
    Affected if The version shown is 10.0, 11.0, 12.0, 12.1, or 13.0 (exact match to affected versions)
  2. Check Security Patch Level
    Go to Settings > About Phone > Security patch level and note the date of the installed security update
    Affected if The security patch level is dated before the CVE-2022-20451 fix was released (typically November 2022 or earlier for affected versions)
  3. Verify telephony framework state
    Review system logs for any calls to the onCallRedirectionComplete method in CallsManager; on Android, use 'adb logcat' with grep for 'CallsManager' or check /system/log for relevant entries if accessible
    Affected if Logs show unpermissioned calls to onCallRedirectionComplete with no permission enforcement visible

A device is affected if it runs Android 10.0, 11.0, 12.0, 12.1, or 13.0 AND the installed security patch predates the November 2022 Android security update that addresses this vulnerability.

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 Android security updates for affected versions (Android-10 through Android-13) as they become available from device OEMs; this is a platform-level vulnerability requiring a system patch from Google.

Recommended fix High confidence

Android 12L (S) or Android 13 with December 2022 security patch level

  1. 1. Check current Android version: Go to Settings > About Phone > Android version or Software version
  2. 2. Check current security patch level: Go to Settings > About Phone > Security patch level
  3. 3. If running Android 10, 11, 12, or 12.1, update the device to receive the December 2022 security patch or later
  4. 4. Navigate to Settings > System > Software Update (or Settings > Security)
  5. 5. Check for updates and install any available system updates
  6. 6. Verify the security patch level is December 2022 or later after the update
Caveat Minimal risk - security updates are backward compatible. Some older devices may not receive further updates.

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20451 — 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-20451 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