Live data from Hacker News

No one, not even the Secret Service, should randomly plug in a strange USB stick

techcrunch.com

71–80 of 231 posts

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#71
Shouldn't preventing this be as easy as turning off autorun? In fact, I thought Windows had that off by default for USB devices.

(Of course, I'm assuming we're not dealing with a zero-day in the USB stack or filesystem drivers. But that probably is something that the Secret Service should be on top of, as well.)

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#72
You can avoid software issues by proper configuration (I want to configure Linux not to automatically enable USB input devices). Of course hardware issues such as damaging the computer is different, but there may be another way to mitigate that. (For several reasons I also do not like the USB so much, though)

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#73

I don't know much about this case but depending on the level of concern, even just plugging the device into a safe, isolated machine and performing an image may be insufficient. You could imagine a USB device that presented as a harmless file store unless certain conditions were detected, in which case the device could re-present as a keyboard (providing pre-programmed keystrokes) or potentially a bluetooth or wirele…

Suppose it is just harmless to the computer, but it uses the USB port to power something else.

It could contain a microphone and a transmitter.

A more evil device, for assassination, could contain explosives or nerve gas. Plugging in the device is fatal.

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#74

Earlier quoted context omitted.

One small example: KVM switches would become incredibly cumbersome to use. However, I agree, there should be a much higher security standard for USB devices on the OS-level.

There are some implementation details that the KVM maker would have to get right, but if they don't screw it up, it all works as expected. Good KVMs already look at the keyboards they have connected, present separate virtual keyboards to connected computers, and route keystrokes explicitly based on state. You just need them to count the keyboards connected to them, and present a separate virtual keyboard for each dow…

That makes sense, guess I never really took time to think about it or inspect.

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#76

Earlier quoted context omitted.

The keyboard trick is quite a hack, but creative. At the same time afaik most barcode scanners also act as keyboards, you scan a number, it "types in" those numbers. I can't see how the filesystem hack would work, if the OS has the drive mounted, it would cache files in memory, and not notice the file contents changing. You can't even modify the metadata, because most of that might also be in memory.

Before chip embedded credit/debit cards were prevalent, most magnetic strip reader (MSR) peripherals would often operate as a USB keyboard. It allows them to work with web app based POS systems without requiring things like ActiveX.

In high school we messed around with this in the crappy P.O.S. system at the place I worked (windowed app, running on Windows) to see what data was recorded on all our various student ID cards, gift certificates etc.

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#77
post #33

Earlier quoted context omitted.

The keyboard trick is quite a hack, but creative. At the same time afaik most barcode scanners also act as keyboards, you scan a number, it "types in" those numbers. I can't see how the filesystem hack would work, if the OS has the drive mounted, it would cache files in memory, and not notice the file contents changing. You can't even modify the metadata, because most of that might also be in memory.

Emulate a MTP device (often used by cameras) and mount with a fuse driver. Since the content on the remote device can change the driver shouldn't be caching it.

Or emulate a network, generate a DHCP response for your favorite /31 and don't send a router, and point a public domain name at the other address in that /31.

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#78
post #49
post #19

Earlier quoted context omitted.

The Secret Service as an organization has sophisticated cyber capabilities. That a specific agent within the president's detail didn't is less surprising. Still, I'd expect more from the organization, and I bet that the specific agents involved are getting disciplined and trained.

Well, the head of USSS was fired today. Unclear if it's related.

I'm of the opinion that a POTUS that carries a unsecured iPhone against the recommendations of his staff (and overrules their security clearance decisions for his son-in-law) isn't going to fire anyone due to quibbles over OPSEC.

Re: No one, not even the Secret Service, should randomly plug in a strange USB stick

#80

Shouldn't preventing this be as easy as turning off autorun? In fact, I thought Windows had that off by default for USB devices. (Of course, I'm assuming we're not dealing with a zero-day in the USB stack or filesystem drivers. But that probably is something that the Secret Service should be on top of, as well.)

Good question. As I understand it, the USB stick can present itself as a keyboard, which is automatically mounted, and begins entering a series of keystrokes that program the system to compromise itself.

In essence, modern OS's give "autorun" privilege to keyboards and mice. That's the HID in this discussion -- Human Interface Device.

Post reply on HN