Four French and Belgian security researchers claim that an online user’s privacy can be compromised because websites receive very specific data about how long it will take for a battery to die out as well as the capacity of the remaining battery. When these two numbers are taken together, what websites get is an ID number which can be used to identify browsers across websites.
Read: Apple pushed down to 3rd in China smartphones for Q2
Those who use a private browsing option are not safe either. The researchers said, “Users who try to revisit a website with a new identity may use browsers’ private mode or clear cookies and other client side identifiers. When consecutive visits are made within a short interval, the website can link users’ new and old identities by exploiting battery level and charge or discharge times. The website can then reinstantiate users’ cookies and other client side identifiers, a method known as respawning.”
The researchers also found that on some platforms, it is possible to determine the maximum battery capacity of the device with enough queries which creates a semi-permanent metric to compare devices.
In 2012, the World Wide Consortium (W3C) had introduced the battery status API, which is supported in the Firefox, Opera and Chrome browsers. Its purpose was to help online users conserve their battery power. This enables a website and web app to notice when a visitor has limited battery power left and shift to a low-power mode by disabling minor features to help preserve energy.
Read: Is Android behind Samsung's fall in the smartphone market?
Further, websites do not even ask the user’s permission to find out how much battery life is left because, according to the W3C “the information disclosed has minimal impact on privacy or fingerprinting, and therefore is exposed without permission grants”.
However, the recent research has raised doubts about the W3C’s claims.
This article originally appeared on The Guardian.
COMMENTS (1)
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ