Endpoint //

Privacy

12/8/2018
09:51 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
100%
0%

'PowerSnitch' Hacks Androids via Power Banks

Researcher demonstrates how attackers could steal data from smartphones while they're charging.

BLACK HAT EUROPE – London – An inexpensive Android hacking tool can create a covert communications channel in the power current generated while a smartphone charges on a power bank.

The so-called "PowerSnitch" attack, which was demonstrated here this week by Oxford University researcher Riccardo Spolaor, shows that a determined hacker doesn't actually need a network connection to hack a targeted smartphone and steal stored data such as passwords. Public power banks, and even private power bank devices, are vulnerable to the attack – which works even when the phone is equipped with a data-blocker device for protecting the data pin in the phone's power port.

PowerSnitch consists of both the app and a £17 (US $23.64) decoder device that translates the power signal via GNURadio to the data it siphons. The portable decoder is a stealthier version of a large prototype Spolaor and his fellow researchers – Laila Abudahi and professor Radha Poovendran of the University of Washington, professor Ivan Martinovic of Oxford, and Elia Dal Santo of the University of Padua in Italy – built in 2017 to hack into Android via the power charge.

"We used a big device [then]," Spolaor said. "So this time we wanted to see something less powerful and cheaper and even [more] deployable everywhere."

PowerSnitch is a targeted attack that requires the attacker to either lure the victim into downloading the malicious app (disguised as a legitimate one, such as an alarm clock) or to manually load the app on the victim's smartphone. "Everything depends on the attacker," Spolaor said. "He has to know his target in advance" and get the PowerSnitch onto the victim's Android somehow. Then he can exfiltrate data via power consumption. He could look at the phone's memory for stored passwords, contact lists, and photos, for example.

The decoder is slipped into the power bank, he said, and can be deployed in a power-port socket. The device consists of a sensor, Wi-Fi module, micro SD card, and SPI card reader.

The data exfiltration rate is low, at around 2 bits per second, he said, due to the power burst delay in the charging process. PowerSnitch, in effect, "turns the smartphone into a telegraph" that grabs the binary information from the current, he said.

"It's using only the surplus current, so it doesn't affect the battery recharging," he said.

Protecting an Android phone from such an attack via tampered power banks is really simple: Just power off the phone when charging it.

The researchers also plan to study whether the Apple iPhone is susceptible to the attack.

Related Content:

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
cuminhgencorp
50%
50%
cuminhgencorp,
User Rank: Apprentice
12/22/2018 | 2:39:10 AM
Can't believe this
So, it must be harsh
pdcz
50%
50%
pdcz,
User Rank: Apprentice
12/11/2018 | 6:06:53 AM
Re: Whats the point?
Still if you are able to trick anyone to install your app then transferring data over power charger seems to me as un-necessary burden. Anyway it is good reminder that there are multiple paths how to obtain data from devices. Personally I would not use any public charger station :-)
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
12/10/2018 | 4:22:30 PM
Re: Whats the point?
As the researchers noted, it's a VERY targeted attack. Their main point was that you can abuse the process of power-charging, and that power banks aren't necessarily safe. 
pdcz
50%
50%
pdcz,
User Rank: Apprentice
12/10/2018 | 5:25:51 AM
Whats the point?
Technologicaly interesting but for the real world attack I would compare it to transferring your company's sensitive materials by using laser pointer and blinking the information encoded into morse code through the office window. If you already have a "ttrojan" app on the phone...
Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6455
PUBLISHED: 2019-01-16
An issue was discovered in GNU Recutils 1.8. There is a double-free problem in the function rec_mset_elem_destroy() in the file rec-mset.c.
CVE-2019-6456
PUBLISHED: 2019-01-16
An issue was discovered in GNU Recutils 1.8. There is a NULL pointer dereference in the function rec_fex_size() in the file rec-fex.c of librec.a.
CVE-2019-6457
PUBLISHED: 2019-01-16
An issue was discovered in GNU Recutils 1.8. There is a memory leak in rec_aggregate_reg_new in rec-aggregate.c in librec.a.
CVE-2019-6458
PUBLISHED: 2019-01-16
An issue was discovered in GNU Recutils 1.8. There is a memory leak in rec_buf_new in rec-buf.c when called from rec_parse_rset in rec-parser.c in librec.a.
CVE-2019-6459
PUBLISHED: 2019-01-16
An issue was discovered in GNU Recutils 1.8. There is a memory leak in rec_extract_type in rec-utils.c in librec.a.