Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App sends persistent device identifier in the clear in Bluetooth frames #536

Open
doug-leith opened this issue Dec 21, 2020 · 0 comments
Open

Comments

@doug-leith
Copy link

The app sends the DiD value in the clear in Bluetooth frames. This value is linked to the phone number and device Android ID and so acts as long-lived, persistent identifier of the handset. By sending this in the clear, an attacker monitoring Bluetooth frames can potentially track users movements over time.

Note that due to such concerns the Google/Apple Exposure Notification system frequently changes the identifier broadcast in Bluetooth frames, and similarly most other apps (the Singapore and Australian apps for example).

Commercial providers are already seeking to build bluetooth sensor networks specifically targetting COVID-19 surveillance of this sort by embedding SDK code within common apps, e.g. see www.cuebiq.com/visitation- insights- covid19 and arxiv.org/pdf/2009.06077.pdf.

We therefore recommend that the app be modified to frequently change the broadcast identifier so as to mitigate such linking attacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant