Adjacent code execution via NFC routing size overflow
Published Apr 19, 2023 · Updated Feb 5, 2025
Out-of-bounds write in Android 11, 12, 12L, and 13 allows physically proximate attackers to execute code through crafted NFC routing data. The nci_snd_set_routing_cmd function in nci_hmsgs.cc calculates an eight-bit routing payload size without checking whether tlv_size plus two overflows, then copies the declared TLV bytes into the undersized command buffer. An attacker within NFC range needs no privileges or user interaction; successful memory corruption grants code execution in the NFC system context.
Summary
What happened
Out-of-bounds write in Android 11, 12, 12L, and 13 allows physically proximate attackers to execute code through crafted NFC routing data. The nci_snd_set_routing_cmd function in nci_hmsgs.cc calculates an eight-bit routing payload size without checking whether tlv_size plus two overflows, then copies the declared TLV bytes into the undersized command buffer. An attacker within NFC range needs no privileges or user interaction; successful memory corruption grants code execution in the NFC system context.
The record
- CVE
- CVE-2023-21085
- Published
- Apr 19, 2023
- Updated
- Feb 5, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1477
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 2023CVE publishedPublication date reported by the CVE source.
- Feb 5, 2025Record 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-11 Android-12 Android-12L Android-13
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.
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