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

add random delay #496

Closed
egberts opened this issue Nov 12, 2022 · 2 comments
Closed

add random delay #496

egberts opened this issue Nov 12, 2022 · 2 comments
Labels

Comments

@egberts
Copy link

egberts commented Nov 12, 2022

#Abstract

Mobile instant messengers such as WhatsApp use delivery status notifications in order to inform users if a sent message has successfully reached its destination. This is useful and important information for the sender due to the often asynchronous use of the messenger service. However, as we demonstrate in this paper, this standard feature opens up a timing side channel with unexpected consequences for user location privacy.

We investigate this threat conceptually and experimentally for three widely spread instant messengers. We validate that this information leak even exists in privacy-friendly messengers such as Signal and Threema.

Our results show that, after a training phase, a messenger user can distinguish different locations of the message receiver.

Our analyses involving multiple rounds of measurements and evaluations show that the timing side channel persists indepen- dent of distances between receiver locations – the attack works both for receivers in different countries as well as at small
scale in one city.

For instance, out of three locations within the same city, the sender can determine the correct one with more than 80 % accuracy.

Thus, messenger users can secretly spy on each others’ whereabouts when sending instant messages. As our countermeasure evaluation shows, messenger providers could effectively disable the timing side channel by randomly delaying delivery confirmations within the range of a few seconds. For users themselves, the threat is harder to prev

https://arxiv.org/pdf/2210.10523.pdf

@stale
Copy link

stale bot commented Mar 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 5, 2023
@stale
Copy link

stale bot commented Mar 14, 2023

This issue has been closed due to inactivity.

@stale stale bot closed this as completed Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants
@egberts and others