Bluetooth pairing consent bypass via CRLF injection
Published Jul 14, 2021 · Updated Aug 3, 2024
CRLF injection in Android 8.1 through 11 allows physically proximate attackers to bypass Bluetooth pairing consent through a crafted NFC message. ConfirmConnectActivity.onCreate displays an unvalidated Bluetooth device name from the NDEF message, allowing embedded CRLF characters to alter the confirmation text. An attacker must bring an NFC payload into range and persuade the user to approve the deceptive prompt; successful exploitation establishes the Bluetooth connection.
Summary
What happened
CRLF injection in Android 8.1 through 11 allows physically proximate attackers to bypass Bluetooth pairing consent through a crafted NFC message. ConfirmConnectActivity.onCreate displays an unvalidated Bluetooth device name from the NDEF message, allowing embedded CRLF characters to alter the confirmation text. An attacker must bring an NFC payload into range and persuade the user to approve the deceptive prompt; successful exploitation establishes the Bluetooth connection.
The record
- CVE
- CVE-2021-0594
- Published
- Jul 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-74, T1404
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 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-11 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
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