CVE-2020-0022
CVE-2020-0022 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-682.
Key facts
- Severity: High (CVSS 3.x base score 8.8)
- CVSS v2: 8.3
- EPSS exploit prediction: 5% (92nd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-682
- Affected product: Google Android
- Published:
- Last modified:
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
Frequently asked questions
- What is CVE-2020-0022?
- 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
- How severe is CVE-2020-0022?
- CVE-2020-0022 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over an adjacent network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2020-0022 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (92nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2020-0022?
- CVE-2020-0022 primarily affects Google Android. In total, 25 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2020-0022?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2020-0022 published?
- CVE-2020-0022 was published on 2020-02-13 and last updated on 2026-06-17.
References
- http://packetstormsecurity.com/files/156891/Android-Bluetooth-Remote-Denial-Of-Service.html
- http://seclists.org/fulldisclosure/2020/Feb/10
- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200513-03-smartphone-en
- https://source.android.com/security/bulletin/2020-02-01
Affected products (25)
- cpe:2.3:o:google:android:8.0:*:*:*:*:*:*:*
- cpe:2.3:o:google:android:8.1:*:*:*:*:*:*:*
- cpe:2.3:o:google:android:9.0:*:*:*:*:*:*:*
- cpe:2.3:o:google:android:10.0:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_20_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_20_pro_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_20_x_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:p_smart_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:p_smart_2019_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:p20_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:p20_pro_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:p30_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:p30_pro_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:y6_2019_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:y6_pro_2019_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:y9_2019_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:nova_3_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:nova_lite_3_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:honor_8a_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:honor_8x_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:honor_view_20_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_30_pro_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_30_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_30_pro_5g_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:mate_30_5g_firmware:*:*:*:*:*:*:*:*
More vulnerabilities in Google Android
- CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
- CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
- CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
- CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
- CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
- CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…
All CVEs affecting Google Android →
Other CWE-682 vulnerabilities
- CVE-2023-2163 — Critical (CVSS 10.0): Incorrect verifier pruning in BPF in Linux Kernel >=5.4 leads to unsafe code paths being incorrectly marked as safe,…
- CVE-2026-1229 — Critical (CVSS 9.8): The CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific…
- CVE-2024-36736 — Critical (CVSS 9.8): An issue in the oneflow.permute component of OneFlow-Inc. Oneflow v0.9.1 causes an incorrect calculation when the same…
- CVE-2022-30600 — Critical (CVSS 9.8): A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout…
- CVE-2021-44847 — Critical (CVSS 9.8): A stack-based buffer overflow in handle_request function in DHT.c in toxcore 0.1.9 through 0.1.11 and 0.2.0 through…
- CVE-2020-0221 — Critical (CVSS 9.8): Airbrush FW's scratch memory allocator is susceptible to numeric overflow. When the overflow occurs, the next…