# CVE-2022-20214: Security feature bypass in Android

> Attackers can use tapjacking to bypass user consent and modify system settings in the Android Car Settings app.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jan 2023
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-2c4q-pqm9-78g4

## What is CVE-2022-20214?

CVE-2022-20214 is a medium-severity vulnerability in Google Android, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Car Settings app, the toggle button in Modify system settings is vulnerable to tapjacking attack. Attackers can overlay the toggle button to enable apps to modify system settings without user consent.Product: AndroidVersions: Android-10 Android-11 Android-12Android ID: A-183411210

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2022-20214?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2022-20214?

No fix has been published for CVE-2022-20214 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-20214 being exploited?

There is no known exploitation of CVE-2022-20214 in the wild and no public exploit code.

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-20214 and fix it if it is affected.

What it is: CVE-2022-20214 is a medium-severity vulnerability in Google Android, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-20214 in the wild and no public exploit code.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-20214/ (Markdown: https://insights.sbomify.com/CVE-2022-20214/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-20214
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-20214
- OSV: https://osv.dev/vulnerability/CVE-2022-20214

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-20214/
Summaries are generated and may contain mistakes; the official description above is the record.