Welcome to HBH! If you had an account on hellboundhacker.org you will need to reset your password using the Lost Password system before you will be able to login.

Poisoned smartphone batteries can act as keyloggers


Poisoned smartphone batteries can act as keyloggers

Power trace sniffing, a badly-designed API and some cloudy AI spell potential trouble.

A group of researchers has demonstrated that smartphone batteries can offer a side-channel attack vector by revealing what users do with their devices through analysis of power consumption.

Both snitching and exfiltration were described in this paper *(PDF), accepted for Julys Privacy Enhancing Technologies Symposium.

Nobody needs to panic yet, because the attack is not yet more than a decently-tested theory and it would be hard to execute. But there is also a real-world implication because the paper shows how a too-free API can help attackers in ways its designers never imagined.

The paper, by researchers from UT Austin, the Hebrew University, and Technion explained that a poisoned battery can gather enough information about power-hungry phone components to reveal user activity.


In their research, they turned a battery into a snitch by implanting a microcontroller to sample power flowing in and out at a 1 kHz sample rate.

The battery, they wrote, is a very attractive attack vector because all the phone activity is exposed. An attacker can correlate power flows with a keystroke, the context of the keystroke (is someone visiting a Website at the time?) and the events that preceded or followed it, such as taking a photo or making a phone call.

Together, these pieces of information reconstruct a coherent portrait of the users activity, dramatically amplifying the power of individual attacks, the paper states.

The authors contend that reading the CPU and screens power traces (and even those from the GPU or the DRAM in some cases) would reveal information about Websites a user visited, or even what they were typing on the screen.

As an attack, it is relatively clumsy. An attacker would have to insert their poisoned battery – which is, however, feasible if you have had to hand a phone over to someone with legal authority or for repair. The attack also needs an offline AI to learn how to classify the power traces.

However what is not theoretical is the exfiltration path – the Web Battery API, criticised as offering snitching options, and abandoned by Mozilla and Webkit for that reason.

Looking over the paper, privacy consultant Lukasz Olejnik summarised the exfiltration route: All the victim user has to do is to visit a sink website that is reading the data. Malicious batteries can detect when the browser enters this special website, and enable the exfiltration mode.

The paper noted that the update rate is not limited in the browser the researchers tested (the built-in Chrome-based browser on a Huawei and two Samsung phones), making the manufacturers design choice in the charger the factor that limited updates (exfiltration in the experiment was slow, at 0.17 bit/second, but the paper offers suggestions for improvement).

As Olejnik wrote: there is no reason for browsers to allow frequent switches between charge/discharge events. So Privacy by Design methodology would advise here: that the switch rate should be capped.

*Download the PDF here:   https://sites.google.com/site/silbersteinmark/Home/popets18power.pdf

Comments
Sorry but there are no comments to display