Device tracking via asynchronous Bluetooth identifier rotation
Published Jun 11, 2020 · Updated Aug 4, 2024
Information disclosure in the Apple/Google Exposure Notification API beta through 2020-05-29 allows attackers to track nearby devices. The claim states that some Android Bluetooth implementations rotate the advertiser address out of sync with the Rolling Proximity Identifier, linking broadcasts across rollover. Bluetooth proximity and passive beacon capture are required; the record is disputed because the specification requires synchronous rotation, although Google confirmed the behavior on a subset of Android devices.
Summary
What happened
Information disclosure in the Apple/Google Exposure Notification API beta through 2020-05-29 allows attackers to track nearby devices. The claim states that some Android Bluetooth implementations rotate the advertiser address out of sync with the Rolling Proximity Identifier, linking broadcasts across rollover. Bluetooth proximity and passive beacon capture are required; the record is disputed because the specification requires synchronous rotation, although Google confirmed the behavior on a subset of Android devices.
The record
- CVE
- CVE-2020-13702
- Published
- Jun 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1040
- 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Exposure Notification vulnerability technical report dated 2020-06-16proof of concept · demonstrated
- Exposure Notification vulnerability second technical report dated 2020-06-16proof of concept · demonstrated
- Exposure Notification vulnerability technical report dated 2020-06-11proof 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