Remote code execution via unchecked NFC response length
Published Jun 11, 2020 · Updated Aug 4, 2024
Out-of-bounds write in Android 10's NFC Type 4 Tag reader allows remote attackers to execute code through a crafted NFC response. The rw_t4t.cc presence-check path processes a received response without first enforcing the required buffer length, allowing memory to be written outside its bounds. An attacker must supply crafted NFC Type 4 Tag data within radio range; no privileges or user interaction are required, and successful exploitation executes code in the NFC process context.
Summary
What happened
Out-of-bounds write in Android 10's NFC Type 4 Tag reader allows remote attackers to execute code through a crafted NFC response. The rw_t4t.cc presence-check path processes a received response without first enforcing the required buffer length, allowing memory to be written outside its bounds. An attacker must supply crafted NFC Type 4 Tag data within radio range; no privileges or user interaction are required, and successful exploitation executes code in the NFC process context.
The record
- CVE
- CVE-2020-0217
- Published
- Jun 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 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-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
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