dbcve.org
AndroidOperating system · Google

CVE-2022-20429

HIGH · 8.8 CVSS v3.1 Published 2022-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 CarSettings of app packages, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege in Bluetooth settings with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-220741473

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 confused deputy vulnerability in Android's CarSettings application allows a local attacker to bypass permission checks and escalate privileges to modify Bluetooth settings without user interaction or additional execution privileges. The attacker exploits the trusted CarSettings component's elevated permissions to access sensitive Bluetooth configuration functions.

MitigationApply the vendor security patch for CVE-2022-20429 (Android Security Bulletin) to affected devices running Android 10-12L. Since this is a platform-level vulnerability in the CarSettings system app, no code-level remediation is possible by end-user organizations—they must await and deploy the official Google/Android system update.

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

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/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 version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is 10, 11, 12.0, or 12.1
  2. Verify Android 12L/SV2 status
    Check if version shows 12L (12.1) or run 'getprop ro.build.version.sdk' - affected versions are SDK 29-32
    Affected if SDK version is 29, 30, 31, or 32
  3. Confirm CarSettings application presence
    Check for com.android.car.settings package via 'pm list packages | grep car.settings' in ADB shell, or look for CarSettings in app list on automotive head units
    Affected if CarSettings app is installed and enabled on the device

A device is affected if it runs Android 10, 11, 12.0, or 12.1 with the CarSettings application present, which is typical on Android Automotive OS infotainment systems.

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 vendor security patch for CVE-2022-20429 (Android Security Bulletin) to affected devices running Android 10-12L. Since this is a platform-level vulnerability in the CarSettings system app, no code-level remediation is possible by end-user organizations—they must await and deploy the official Google/Android system update.

Recommended fix Moderate confidence

Android 13 (API 33) or later

  1. 1. Verify the current Android version on the affected device by going to Settings > About Phone > Android version
  2. 2. Back up all important data on the device before proceeding with the upgrade
  3. 3. Check for system updates by navigating to Settings > System > Software Update > Check for updates
  4. 4. If Android 13 (API 33) is available, download and install the update
  5. 5. After installation, verify the device is running Android 13 by checking Settings > About Phone > Android version
  6. 6. Confirm the Bluetooth settings function correctly after the upgrade
Caveat Major Android version upgrade may have compatibility implications with existing apps, settings, and workflows; review app compatibility and backup data before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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