Home/CVE/In reassemble_and_dispatch of packet_fragmenter.cc, there is possible out of bounds write due to an incorrect bounds cal
CVE
CVE-2020-002216
In reassemble_and_dispatch of packet_fragmenter.cc, there is possible out of bounds write due to an incorrect bounds cal
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.
HIGH · CVSS 8.8
EPSS 0.05379
EPSS exploitation odds5.38% · top 8%
Act now
- EPSS percentile: top 8% of all CVEs by exploitation likelihood
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2020-0022, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠
Exploitation evidence
1 of 7 sources
Corroboration score 8/100 ·
emerging.
This counts how many independent sources have exploitation evidence, and separates two different things:
confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from
exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means
an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗
Exploitation momentum
1237 days of EPSSstable
Exploitation pressure is steady. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
5.38%
Top 8%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
no
Tech impact
total
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLifecycle
- 13 Feb 2020Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
⚠
Public Exploits & PoCs
16These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Source
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
poc
packetstormsecurity.com · Android-Bluetooth-Remote-Denial-Of-Service.html↗
packetstormsecurity.com
Works?
no reports yet
Rating
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
2Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Products & Versions
22google androidall versions
huawei mate 20 firmware< 10.0.0.195\(c00e74r3p8\)
huawei mate 20 pro firmware< 10.0.0.196\(c185e7r2p4\)
huawei mate 20 x firmware< 10.0.0.195\(c00e74r2p8\)
huawei p smart firmware< 9.1.0.193\(c605e6r1p5t8\)
huawei p smart 2019 firmware< 10.0.0.180\(c185e3r4p1\)
huawei p20 firmware< 10.0.0.162\(c00e156r1p4\)
huawei p20 pro firmware< 10.0.0.162\(c00e156r1p4\)
huawei p30 firmware< 10.0.0.190\(c432e22r2p5\)
huawei p30 pro firmware< 10.0.0.195\(c00e85r2p8\)
huawei y6 2019 firmware< 9.1.0.290\(c185e5r4p1\)
huawei y6 pro 2019 firmware< 9.1.0.290\(c636e5r3p1\)
huawei y9 2019 firmware< 9.1.0.264\(c185e2r5p1t8\)
huawei nova 3 firmware< 9.1.0.338\(c00e333r1p1t8\)
huawei nova lite 3 firmware< 9.1.0.322\(c635e8r2p2\)
huawei honor 8a firmware< 9.1.0.291\(c185e3r4p1\)
huawei honor 8x firmware< 10.0.0.183\(c185e2r6p1\)
huawei honor view 20 firmware< 10.0.0.195\(c636e3r4p3\)
huawei mate 30 pro firmware< 10.0.0.203\(c00e202r7p2\)
huawei mate 30 firmware< 10.0.0.203\(c00e202r7p2\)
huawei mate 30 pro 5g firmware< 10.0.0.203\(c00e202r7p2\)
huawei mate 30 5g firmware< 10.0.0.203\(c00e202r7p2\)
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2011-1573
net/sctp/sm_make_chunk.c in the Linux kernel before 2.6.34, when addip_enable an...
same CWE-682
MEDIUM
CVE-2011-3062
Off-by-one error in the OpenType Sanitizer in Google Chrome before 18.0.1025.142...
same CWE-682
CVE-2016-7433
NTP before 4.2.8p9 does not properly perform the initial sync calculations, whic...
same CWE-682
MEDIUM
CVE-2016-9377
Xen 4.5.x through 4.7.x on AMD systems without the NRip feature, when emulating ...
same CWE-682
MEDIUM
CVE-2019-9506
The Bluetooth BR/EDR specification up to and including version 5.1 permits suffi...
same product
HIGH
CVE-2019-5292
Honor 10 Lite, Honor 8A, Huawei Y6 mobile phones with the versions before 9.1.0....
same product
LOW
CVE-2020-0069
In the ioctl handlers of the Mediatek Command Queue driver, there is a possible ...
same product
HIGH
CVE-2019-5252
There is an improper authentication vulnerability in Huawei smartphones (Y9, Hon...
same product
LOW
⚑
Vendor Advisories
1🔗
References & Sources
3Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.