dbcve.org
AndroidOperating system · Google

CVE-2022-20466

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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 applyKeyguardFlags of NotificationShadeWindowControllerImpl.java, there is a possible way to observe the user's password on a secondary display due to an insecure default value. This could lead to local information disclosure 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-179725730

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

In applyKeyguardFlags of NotificationShadeWindowControllerImpl.java, an insecure default value causes the user's lock screen password to be potentially visible on secondary displays (e.g., cast, wireless display, external monitor). This allows local information disclosure when a secondary display is active, requiring user interaction but no additional execution privileges.

MitigationThe fix requires updating the default keyguard flag handling in NotificationShadeWindowControllerImpl to properly secure secondary display output. Users should apply the Android security patch level that addresses CVE-2022-20466.

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= 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
None
Availability
None

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

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

  1. Verify Android version is affected
    Go to Settings > About Phone > Android version, or run: adb shell getprop ro.build.version.release
    Affected if Version is 10.0, 11.0, 12.0, or 13.0
  2. Check for active wireless display or Cast session
    Open Settings > Display > Cast (or search 'Cast'), or run: adb shell dumpsys display | grep -i 'mScreen'
    Affected if A wireless display, Cast session, or external monitor is currently connected or was recently active
  3. Confirm screen casting is enabled
    Access Settings > Network & Internet > Cast, or navigate to the quick settings panel and look for the Cast icon
    Affected if Screen casting or wireless display functionality is turned on or has been used on this device

The device is affected if it runs Android 10.0, 11.0, 12.0, or 13.0 AND has screen casting, wireless display, or external monitor connectivity enabled or active.

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

The fix requires updating the default keyguard flag handling in NotificationShadeWindowControllerImpl to properly secure secondary display output. Users should apply the Android security patch level that addresses CVE-2022-20466.

Recommended fix High confidence

Android 13 with November 2022 security patch level, or Android 12L/12 with November 2022 security patch

  1. 1. Navigate to Settings > System > System Update (or Settings > Security & Privacy > Security Update on some devices)
  2. 2. Check for and install any available system updates
  3. 3. Verify the security patch level is November 2022 or later by going to Settings > About Phone > Android version (or Settings > System > Security > Security update)
  4. 4. Confirm the installed security patch includes the fix for CVE-2022-20466
Caveat Minimal risk - security updates typically have no functional breaking changes; however, older devices may not receive the update

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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