# CVE-2021-0315: Security feature bypass in Android

> Attackers can use tapjacking to trick users into granting account access, leading to local privilege escalation on Android devices.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** A-169763814, ASB-A-169763814, GHSA-jwx3-h29g-4mcg

## What is CVE-2021-0315?

CVE-2021-0315 is a high-severity vulnerability in Google Android, published on 11 Jan 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In onCreate of GrantCredentialsPermissionActivity.java, there is a possible way to convince the user to grant an app access to an account due to a tapjacking/overlay attack. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed for exploitation. Product: Android; Versions: Android-8.1, Android-9, Android-10, Android-11, Android-8.0; Android ID: A-169763814.

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

## Which versions are affected by CVE-2021-0315?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2021-0315?

Apply the vendor's patch.

## Is CVE-2021-0315 being exploited?

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

Public exploit code:

- https://github.com/nanopathi/framework_base_AOSP10_r33_CVE-2021-0315 (github_poc): https://github.com/nanopathi/framework_base_AOSP10_r33_CVE-2021-0315
- https://github.com/pazhanivel07/frameworks_base_Aosp10_r33_CVE-2021-0315 (github_poc): https://github.com/pazhanivel07/frameworks_base_Aosp10_r33_CVE-2021-0315
- https://github.com/nanopathi/frameworks_base1_CVE-2021-0315 (github_poc): https://github.com/nanopathi/frameworks_base1_CVE-2021-0315

## 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-2021-0315 and fix it if it is affected.

What it is: CVE-2021-0315 is a high-severity vulnerability in Google Android, published on 11 Jan 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-0315 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-2021-0315/ (Markdown: https://insights.sbomify.com/CVE-2021-0315/index.md)
```

## Sources

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

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