Code execution via unchecked secondary device-type copy
Published Feb 10, 2021 · Updated Aug 3, 2024
Out-of-bounds write in Google Cloud Android 8.1 through 11 allows physically proximate attackers to execute code via Wi-Fi Direct. p2p_copy_client_info copies an attacker-controlled secondary device-type list into a fixed peer-entry area without checking its length, overwriting adjacent heap pointers. Exploitation requires radio proximity and active P2P discovery; it needs neither authentication nor user interaction and can crash wpa_supplicant or run arbitrary code.
Summary
What happened
Out-of-bounds write in Google Cloud Android 8.1 through 11 allows physically proximate attackers to execute code via Wi-Fi Direct. p2p_copy_client_info copies an attacker-controlled secondary device-type list into a fixed peer-entry area without checking its length, overwriting adjacent heap pointers. Exploitation requires radio proximity and active P2P discovery; it needs neither authentication nor user interaction and can crash wpa_supplicant or run arbitrary code.
The record
- CVE
- CVE-2021-0326
- Published
- Feb 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-120, CWE-787, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
- Affected versionversion=Android-10 Android-11 Android-8.1 Android-9
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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