Access restriction bypass via retained temporary link key
Published Feb 21, 2020 · Updated Aug 6, 2024
Incorrect authorization in Google Android before 5.1 allows remote attackers to bypass access restrictions through Bluetooth pairing. The btif/src/btif_dm.c pairing control block treats an unset temporary-pairing flag as persistent, causing a temporary link key to be stored. Exploitation requires a user to tap a crafted NFC tag and then process crafted Bluetooth packets, after which the unintended persistent bond retains access.
Summary
What happened
Incorrect authorization in Google Android before 5.1 allows remote attackers to bypass access restrictions through Bluetooth pairing. The btif/src/btif_dm.c pairing control block treats an unset temporary-pairing flag as persistent, causing a temporary link key to be stored. Exploitation requires a user to tap a crafted NFC tag and then process crafted Bluetooth packets, after which the unintended persistent bond retains access.
The record
- CVE
- CVE-2014-7914
- Published
- Feb 21, 2020
- Updated
- Aug 6, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-863
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=before 5.1
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