CVE-2020-0022

Exp

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

Published: 2020-02-13 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-0022 is rated High Exploit Risk (80.1/100): CVSS High severity, with high exploitation likelihood (EPSS 5.42%, 92th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-0022

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-0022

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 7.58% 5.42% -2.15%
2 2026-05-26 6.95% 7.58% +0.63%
3 2026-02-25 — 6.95% —

Full EPSS history (29 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-0022

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
8.3 2.0 HIGH
AV:A/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 6.5 10.0 [email protected]

Weakness enumeration for CVE-2020-0022

Affected software / configurations for CVE-2020-0022

Vendor Product Version Raw CPE
google android 8.0 cpe:2.3:o:google:android:8.0:*:*:*:*:*:*:*
google android 8.1 cpe:2.3:o:google:android:8.1:*:*:*:*:*:*:*
google android 9.0 cpe:2.3:o:google:android:9.0:*:*:*:*:*:*:*
google android 10.0 cpe:2.3:o:google:android:10.0:*:*:*:*:*:*:*
huawei mate_20_firmware < 10.0.0.195\(c00e74r3p8\) cpe:2.3:o:huawei:mate_20_firmware:*:*:*:*:*:*:*:*
huawei mate_20_pro_firmware < 10.0.0.196\(c185e7r2p4\) cpe:2.3:o:huawei:mate_20_pro_firmware:*:*:*:*:*:*:*:*
huawei mate_20_x_firmware < 10.0.0.195\(c00e74r2p8\) cpe:2.3:o:huawei:mate_20_x_firmware:*:*:*:*:*:*:*:*
huawei p_smart_firmware < 9.1.0.193\(c605e6r1p5t8\) cpe:2.3:o:huawei:p_smart_firmware:*:*:*:*:*:*:*:*
huawei p_smart_2019_firmware < 10.0.0.180\(c185e3r4p1\) cpe:2.3:o:huawei:p_smart_2019_firmware:*:*:*:*:*:*:*:*
huawei p20_firmware < 10.0.0.162\(c00e156r1p4\) cpe:2.3:o:huawei:p20_firmware:*:*:*:*:*:*:*:*
huawei p20_pro_firmware < 10.0.0.162\(c00e156r1p4\) cpe:2.3:o:huawei:p20_pro_firmware:*:*:*:*:*:*:*:*
huawei p30_firmware < 10.0.0.190\(c432e22r2p5\) cpe:2.3:o:huawei:p30_firmware:*:*:*:*:*:*:*:*
huawei p30_pro_firmware < 10.0.0.195\(c00e85r2p8\) cpe:2.3:o:huawei:p30_pro_firmware:*:*:*:*:*:*:*:*
huawei y6_2019_firmware < 9.1.0.290\(c185e5r4p1\) cpe:2.3:o:huawei:y6_2019_firmware:*:*:*:*:*:*:*:*
huawei y6_pro_2019_firmware < 9.1.0.290\(c636e5r3p1\) cpe:2.3:o:huawei:y6_pro_2019_firmware:*:*:*:*:*:*:*:*
huawei y9_2019_firmware < 9.1.0.264\(c185e2r5p1t8\) cpe:2.3:o:huawei:y9_2019_firmware:*:*:*:*:*:*:*:*
huawei nova_3_firmware < 9.1.0.338\(c00e333r1p1t8\) cpe:2.3:o:huawei:nova_3_firmware:*:*:*:*:*:*:*:*
huawei nova_lite_3_firmware < 9.1.0.322\(c635e8r2p2\) cpe:2.3:o:huawei:nova_lite_3_firmware:*:*:*:*:*:*:*:*
huawei honor_8a_firmware < 9.1.0.291\(c185e3r4p1\) cpe:2.3:o:huawei:honor_8a_firmware:*:*:*:*:*:*:*:*
huawei honor_8x_firmware < 10.0.0.183\(c185e2r6p1\) cpe:2.3:o:huawei:honor_8x_firmware:*:*:*:*:*:*:*:*
huawei honor_view_20_firmware < 10.0.0.195\(c636e3r4p3\) cpe:2.3:o:huawei:honor_view_20_firmware:*:*:*:*:*:*:*:*
huawei mate_30_pro_firmware < 10.0.0.203\(c00e202r7p2\) cpe:2.3:o:huawei:mate_30_pro_firmware:*:*:*:*:*:*:*:*
huawei mate_30_firmware < 10.0.0.203\(c00e202r7p2\) cpe:2.3:o:huawei:mate_30_firmware:*:*:*:*:*:*:*:*
huawei mate_30_pro_5g_firmware < 10.0.0.203\(c00e202r7p2\) cpe:2.3:o:huawei:mate_30_pro_5g_firmware:*:*:*:*:*:*:*:*
huawei mate_30_5g_firmware < 10.0.0.203\(c00e202r7p2\) cpe:2.3:o:huawei:mate_30_5g_firmware:*:*:*:*:*:*:*:*

References for CVE-2020-0022

cvelogic Threat Intelligence