# CVE-2022-20234: Missing authorization in Android

> An exported activity in Android Car Settings allows malicious apps to trick users into granting notification access, enabling theft of personal information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v2x4-9328-wv22

## What is CVE-2022-20234?

CVE-2022-20234 is a high-severity missing authorization vulnerability in Google Android, published on 13 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Car Settings app, the NotificationAccessConfirmationActivity is exported. In NotificationAccessConfirmationActivity, it gets both 'mComponentName' and 'pkgTitle' from user.An unprivileged app can use a malicous mComponentName with a benign pkgTitle (e.g. Settings app) to make users enable notification access permission for the malicious app. That is, users believe they enable the notification access permission for the Settings app, but actually they enable the notification access permission for the malicious app.Once the malicious app gets the notification access permission, it can read all notifications, including users' personal information.Product: AndroidVersions: Android-12LAndroid ID: A-225189301

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Google Android.

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

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

## Is CVE-2022-20234 being exploited?

There is no known exploitation of CVE-2022-20234 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-20234 and fix it if it is affected.

What it is: CVE-2022-20234 is a high-severity missing authorization vulnerability in Google Android, published on 13 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-20234 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-20234/ (Markdown: https://insights.sbomify.com/CVE-2022-20234/index.md)
```

## Sources

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

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