Proximity code execution via unchecked NFC tag size
Published Apr 17, 2020 · Updated Aug 4, 2024
Out-of-bounds write in Android 8.0, 8.1, 9, and 10 allows physically proximate attackers to execute code through a crafted NFC tag. In rw_t2t_extract_default_locks_info, a tag-controlled size byte sets num_dynamic_lock_bytes, which then indexes the fixed-size lockbytes buffer without a bounds check. An NFC-enabled device need only process the malicious tag at close range; no user interaction or prior privileges are required, and successful exploitation runs code in the NFC daemon.
Summary
What happened
Out-of-bounds write in Android 8.0, 8.1, 9, and 10 allows physically proximate attackers to execute code through a crafted NFC tag. In rw_t2t_extract_default_locks_info, a tag-controlled size byte sets num_dynamic_lock_bytes, which then indexes the fixed-size lockbytes buffer without a bounds check. An NFC-enabled device need only process the malicious tag at close range; no user interaction or prior privileges are required, and successful exploitation runs code in the NFC daemon.
The record
- CVE
- CVE-2020-0071
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1664, T1658
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=Android-8.0 Android-8.1 Android-9 Android-10
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
- Crafted NFC tag response proof of conceptproof of concept · demonstrated
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