# CVE-2020-0022: Memory corruption in Android

> Remote attackers can execute arbitrary code via Bluetooth due to an out-of-bounds write in the packet fragmenter, requiring no user interaction.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-55v6-vvqw-j3qq

## What is CVE-2020-0022?

CVE-2020-0022 is a high-severity memory corruption vulnerability in Google Android, published on 13 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In reassemble_and_dispatch of packet_fragmenter.cc, there is possible out of bounds write due to an incorrect bounds calculation. This could lead to remote code execution over Bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-143894715

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2020-0022?

It affects 22 products.


Products: Google Android, Huawei Honor 8a Firmware, Huawei Honor 8x Firmware, Huawei Honor View 20 Firmware, Huawei Mate 20 Firmware, Huawei Mate 20 Pro Firmware, Huawei Mate 20 X Firmware, Huawei Mate 30 5g Firmware, Huawei Mate 30 Firmware, Huawei Mate 30 Pro 5g Firmware, Huawei Mate 30 Pro Firmware, Huawei Nova 3 Firmware, Huawei Nova Lite 3 Firmware, Huawei P20 Firmware, Huawei P20 Pro Firmware, Huawei P30 Firmware, Huawei P30 Pro Firmware, Huawei P Smart 2019 Firmware, Huawei P Smart Firmware, Huawei Y6 2019 Firmware and 2 more.

## How do I fix CVE-2020-0022?

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

## Is CVE-2020-0022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-0022 exists.

Public exploit code:

- poc for cve-2020-0022 (github_poc): https://github.com/leommxj/cve-2020-0022
- CVE-2020-0022 vulnerability exploitation on Bouygues BBox Miami (Android TV 8.0 - ARM32 Cortex A9) (github_poc): https://github.com/Polo35/CVE-2020-0022
- This is a RCE bluetooth vulnerability on Android 8.0 and 9.0 (github_poc): https://github.com/k3vinlusec/Bluefrag_CVE-2020-0022
- A fully public exploit of the CVE-2020-0022 BlueFrag Android RCE Vulnerability (tested on Pixel 3 XL) (github_poc): https://github.com/themmokhtar/CVE-2020-0022
- cve-2020-0022相关的一些东西 (github_poc): https://github.com/5k1l/cve-2020-0022
- https://github.com/lsw29475/CVE-2020-0022 (github_poc): https://github.com/lsw29475/CVE-2020-0022

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

What it is: CVE-2020-0022 is a high-severity memory corruption vulnerability in Google Android, published on 13 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-0022 exists.

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-2020-0022/ (Markdown: https://insights.sbomify.com/CVE-2020-0022/index.md)
```

## Sources

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

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