CVE-2020-0022

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6.1%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
6.1%
EPSS %ILE
93rd
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 13, 2020

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Aug 4, 2026
Fix referenced — no release confirmed yet.
generic

Android Security Bulletin—February 2020  |  Android Open Source Project

https://source.android.com/security/bulletin/2020-02-01
generic

Security Advisory - Integer Overflow Vulnerability in Android affects Several Huawei Smartphones

http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200513-03-smartphone-en
generic

Packet Storm Security

http://packetstormsecurity.com/files/156891/Android-Bluetooth-Remote-Denial-Of-Service.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-10-09 20:03 UTCEPSS rescore
  2. 2026-10-08 16:38 UTCEPSS rescore
  3. 2026-10-07 23:43 UTCEPSS rescore
  4. 2026-10-06 15:13 UTCEPSS rescore
  5. 2026-10-05 17:39 UTCEPSS rescore
  6. 2026-10-04 23:18 UTCEPSS rescore
  7. 2026-10-03 14:22 UTCEPSS rescore
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-30 10:30 UTCEG score recompute
  10. 2026-09-27 13:40 UTCEPSS rescore
  11. 2026-09-26 15:54 UTCEPSS rescore
  12. 2026-09-26 00:20 UTCEPSS rescore
  13. 2026-09-24 13:59 UTCEPSS rescore
  14. 2026-09-22 14:43 UTCEPSS rescore
  15. 2026-09-21 20:28 UTCEPSS rescore
  16. 2026-09-20 20:11 UTCEPSS rescore
  17. 2026-09-19 15:37 UTCEPSS rescore
  18. 2026-09-18 19:23 UTCEPSS rescore
  19. 2026-09-17 19:22 UTCEPSS rescore
  20. 2026-09-16 14:04 UTCEPSS rescore
  21. 2026-09-16 14:04 UTCEPSS rescore
  22. 2026-09-15 03:06 UTCEPSS rescore
  23. 2026-09-13 16:42 UTCEPSS rescore
  24. 2026-09-12 14:56 UTCEPSS rescore
  25. 2026-09-11 14:48 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:32 UTCEPSS rescore
  2. 2026-09-07 15:57 UTCEPSS rescore
  3. 2026-09-06 13:44 UTCEPSS rescore
  4. 2026-09-05 15:24 UTCEPSS rescore
  5. 2026-09-04 13:56 UTCEPSS rescore
  6. 2026-09-04 05:03 UTCEPSS rescore
  7. 2026-09-02 14:08 UTCEPSS rescore
  8. 2026-09-01 03:32 UTCEPSS rescore
  9. 2026-08-30 19:14 UTCEPSS rescore
  10. 2026-08-30 01:18 UTCEPSS rescore
  11. 2026-08-28 21:37 UTCEPSS rescore
  12. 2026-08-27 14:21 UTCEPSS rescore
  13. 2026-08-26 14:42 UTCEPSS rescore
  14. 2026-08-25 13:45 UTCEPSS rescore
  15. 2026-08-20 22:51 UTCEPSS rescore
  16. 2026-08-19 17:00 UTCEPSS rescore
  17. 2026-08-18 13:44 UTCEPSS rescore
  18. 2026-08-17 13:43 UTCEPSS rescore
  19. 2026-08-16 14:52 UTCEPSS rescore
  20. 2026-08-16 02:11 UTCEPSS rescore
  21. 2026-08-15 01:26 UTCEPSS rescore
  22. 2026-08-13 21:57 UTCEPSS rescore
  23. 2026-08-12 13:47 UTCEPSS rescore
  24. 2026-08-09 13:43 UTCEPSS rescore
  25. 2026-08-08 16:33 UTCEPSS rescore
  26. 2026-08-07 16:23 UTCEPSS rescore
  27. 2026-08-06 13:43 UTCEPSS rescore
  28. 2026-08-05 19:14 UTCEPSS rescore
  29. 2026-08-04 15:06 UTCEPSS rescore
  30. 2026-08-04 10:34 UTCEPSS rescore
  31. 2026-08-03 10:32 UTCEPSS rescore
  32. 2026-08-02 02:23 UTCEPSS rescore
  33. 2026-08-01 04:12 UTCEPSS rescore
  34. 2026-07-30 16:24 UTCEPSS rescore
  35. 2026-07-30 01:27 UTCEPSS rescore
  36. 2026-07-28 15:32 UTCEPSS rescore
  37. 2026-07-26 14:51 UTCEPSS rescore
  38. 2026-07-25 14:14 UTCEPSS rescore
  39. 2026-07-24 14:14 UTCEPSS rescore
  40. 2026-07-23 14:15 UTCEPSS rescore
  41. 2026-07-23 14:15 UTCEPSS rescore
  42. 2026-07-23 01:47 UTCEG score recompute
  43. 2026-07-22 22:31 UTCEG score recompute
  44. 2026-07-22 14:05 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 17:04 UTCEPSS rescore
  48. 2026-07-19 14:28 UTCEPSS rescore
  49. 2026-07-19 14:28 UTCEPSS rescore
  50. 2026-07-19 02:26 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-18 10:02 UTCEPSS rescore
  53. 2026-07-16 16:59 UTCEPSS rescore
  54. 2026-07-16 16:59 UTCEPSS rescore
  55. 2026-07-15 16:55 UTCEPSS rescore
  56. 2026-07-13 22:27 UTCEPSS rescore
  57. 2026-07-12 05:44 UTCEPSS rescore
  58. 2026-07-11 08:24 UTCEPSS rescore
  59. 2026-07-09 19:06 UTCEPSS rescore
  60. 2026-07-08 15:11 UTCEPSS rescore
  61. 2026-07-07 13:43 UTCEPSS rescore
  62. 2026-07-06 16:25 UTCEPSS rescore
  63. 2026-07-06 16:25 UTCEPSS rescore
  64. 2026-07-06 02:20 UTCEPSS rescore
  65. 2026-07-05 02:27 UTCEPSS rescore
  66. 2026-07-04 06:28 UTCEPSS rescore
  67. 2026-07-01 15:03 UTCEPSS rescore
  68. 2026-07-01 15:03 UTCEPSS rescore
  69. 2026-06-30 23:20 UTCEPSS rescore
  70. 2026-06-30 23:20 UTCEPSS rescore
  71. 2026-06-29 14:04 UTCEPSS rescore
  72. 2026-06-29 14:04 UTCEPSS rescore
  73. 2026-06-28 14:05 UTCEPSS rescore
  74. 2026-06-28 04:54 UTCEPSS rescore
  75. 2026-06-28 04:54 UTCEPSS rescore

Publicly available exploits

(6 references)

Working exploit code is in the public domain (6 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCthemmokhtar/CVE-2020-0022
    First seen Aug 28, 2023

    A fully public exploit of the CVE-2020-0022 BlueFrag Android RCE Vulnerability (tested on Pixel 3 XL)

    Open source ↗
  • GitHub PoClsw29475/CVE-2020-0022
    First seen Feb 24, 2021
    Open source ↗
  • GitHub PoC5k1l/cve-2020-0022
    First seen Dec 16, 2020

    cve-2020-0022相关的一些东西

    Open source ↗
  • GitHub PoCPolo35/CVE-2020-0022
    First seen Aug 24, 2020

    CVE-2020-0022 vulnerability exploitation on Bouygues BBox Miami (Android TV 8.0 - ARM32 Cortex A9)

    Open source ↗
  • GitHub PoCk3vinlusec/Bluefrag_CVE-2020-0022
    First seen Jul 1, 2020

    This is a RCE bluetooth vulnerability on Android 8.0 and 9.0

    Open source ↗
  • GitHub PoCleommxj/cve-2020-0022
    First seen Feb 15, 2020

    poc for cve-2020-0022

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-0022?
CVE-2020-0022 is a high vulnerability published on February 13, 2020. In reassembleanddispatch 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:…
When was CVE-2020-0022 disclosed?
CVE-2020-0022 was first published on February 13, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-0022 actively exploited?
CVE-2020-0022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.1% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-0022?
CVE-2020-0022 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2020-0022?
A fix for CVE-2020-0022 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-0022

Explore →

Is Your Infrastructure Affected by CVE-2020-0022?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs