Remote device re-identification via stale beacon randomness
Published May 18, 2020 · Updated Aug 4, 2024
COVIDSafe v1.0.15 and v1.0.16 allow remote attackers to re-identify Android devices through scanned advertising beacons. The advertising payload fails to reinitialize random data, so repeated beacon values persistently link broadcasts to the same device. Scanning proximity beacons is sufficient; the disclosed impact is indirect confidentiality loss without integrity or availability effects.
Summary
What happened
COVIDSafe v1.0.15 and v1.0.16 allow remote attackers to re-identify Android devices through scanned advertising beacons. The advertising payload fails to reinitialize random data, so repeated beacon values persistently link broadcasts to the same device. Scanning proximity beacons is sufficient; the disclosed impact is indirect confidentiality loss without integrity or availability effects.
The record
- CVE
- CVE-2020-12858
- Published
- May 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 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.
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