CVE-2020-0022Public exploit

Remote code execution via Bluetooth length miscalculation

Published Feb 13, 2020 · Updated Aug 4, 2024

Out-of-bounds write in Android 8.0 through 10 allows physically proximate attackers to execute code or crash Bluetooth via crafted packets. The reassemble_and_dispatch function in packet_fragmenter.cc undercounts an oversized continuing L2CAP packet by omitting the current fragment offset, causing a payload copy beyond the intended buffer. Bluetooth must be enabled, but pairing and user interaction are unnecessary; Android 8.0 through 9 allow privileged-process code execution, while Android 10 is limited to a service crash.

CVSS severity8.8
High
EPSS probability6.05%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds write in Android 8.0 through 10 allows physically proximate attackers to execute code or crash Bluetooth via crafted packets. The reassemble_and_dispatch function in packet_fragmenter.cc undercounts an oversized continuing L2CAP packet by omitting the current fragment offset, causing a payload copy beyond the intended buffer. Bluetooth must be enabled, but pairing and user interaction are unnecessary; Android 8.0 through 9 allow privileged-process code execution, while Android 10 is limited to a service crash.

The record

CVE
CVE-2020-0022
Published
Feb 13, 2020
Updated
Aug 4, 2024
Vendor
Google Cloud
Product
Android
Classifications
CWE-682, T1203
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 13, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Android-8.0 Android-8.1 Android-9 Android-10

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Google Cloud · Androidversion=Android-8.0 Android-8.1 Android-9 Android-10
Google · Androidversion=10.0; version=8.0; version=8.1; version=9.0

Published CVSS scores

8.8CISACVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-682Incorrect Calculation
T1203Exploitation for Client Execution

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo