(no title)
HeavyFeather | 2 years ago
If you want data safety, you must skip the data pins.
If you want current safety, you must skip public chargers.
HeavyFeather | 2 years ago
If you want data safety, you must skip the data pins.
If you want current safety, you must skip public chargers.
tshaddox|2 years ago
yencabulator|2 years ago
paulsutter|2 years ago
epups|2 years ago
retrac|2 years ago
USB is a very intelligent protocol, with a microcontrollor on both ends. The controller has access to at least the driver's state, which is usually in the kernel and potentially has access to system memory.
How does your Android phone even know that data is an option to switch into when you plug it into a USB port? It has already negotiated itself to be a device on the USB bus. Your phone will probably show up in lsusb on Linux even in charging mode. (Mine does.) When you switch the phone to data mode, it changes its USB device profile, and becomes a more sophisticated attached device, from the host's perspective.
Many (most?) phones made in recent years can be USB hosts, too. This lets you connect a USB mouse and keyboard to a tablet, for example. That would open you up to all kinds of pretty simple but often quite effective attacks, like simulating a virtual keyboard and mouse and just manipulating the UI that way.
I don't know if any of these particular attacks are possible with Android right now, but many variations on these themes have been shown over the years on many platforms. USB wasn't really designed with adversarial peripherals in mind.
kccqzy|2 years ago
Not "sharing data" doesn't really mean not sharing data.
StrangeATractor|2 years ago