This is the attack: > If a victim logs into a fake Google site, the phishing site passes on their username and password to the real Google login page. Then the spoofed site passes back Google's request for the user's U2F token and collects the Yubikey's unique answer, all via WebUSB. When that answer is then presented to the real Google site, the attackers gain access to the victim's account. So basically they are so…
Chrome lets hackers phish even 'Unphishable' Yubikey users
41–50 of 113 posts
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#42Earlier quoted context omitted.
It's simple: allowing sandboxed code to request limited access to a USB device is more secure than having users install native, unsandboxed code with access to everything on their PC.
Assuming the sandbox works. If the sandbox is porous, the attack surface balloons from apps I choose to install to every link I click.
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#43Earlier quoted context omitted.
It's simple: allowing sandboxed code to request limited access to a USB device is more secure than having users install native, unsandboxed code with access to everything on their PC.
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=chromium
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#44Earlier quoted context omitted.
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=chromium
As opposed to native desktop apps, which get all the same permissions by default that a web app requires a zero-day sandbox escape vulnerability to achieve?
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#45Earlier quoted context omitted.
As opposed to native desktop apps, which get all the same permissions by default that a web app requires a zero-day sandbox escape vulnerability to achieve?
Native desktop apps are limited in number are nowhere near the dumpster fire the web is. My desktop isn't routinely downloading and executing payloads from the web. They're clearly different.
It comes down to this: if you ever found yourself in a situation where you needed to connect a USB device to a remote service, would you prefer to download that service's unsandboxed native code to your PC and execute it? Or execute some JS in the browser sandbox and grant it limited access to that one specific device?
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#46Earlier quoted context omitted.
Native desktop apps are limited in number are nowhere near the dumpster fire the web is. My desktop isn't routinely downloading and executing payloads from the web. They're clearly different.
This is about the Web USB API, not the entire web in general. Are you routinely granting web pages access to your USB devices? That's not a permission that web apps get by default (unlike with native desktop apps btw). It comes down to this: if you ever found yourself in a situation where you needed to connect a USB device to a remote service, would you prefer to download that service's unsandboxed native code to you…
I have never found myself in that situation. That sounds like a really silly idea.
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#47Earlier quoted context omitted.
This is about the Web USB API, not the entire web in general. Are you routinely granting web pages access to your USB devices? That's not a permission that web apps get by default (unlike with native desktop apps btw). It comes down to this: if you ever found yourself in a situation where you needed to connect a USB device to a remote service, would you prefer to download that service's unsandboxed native code to you…
>if you ever found yourself in a situation where you needed to connect a USB device to a remote service I have never found myself in that situation. That sounds like a really silly idea.
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#48Earlier quoted context omitted.
>if you ever found yourself in a situation where you needed to connect a USB device to a remote service I have never found myself in that situation. That sounds like a really silly idea.
Attaching a bootable USB drive to a HTML5 based KVM? Sure it could be accomplished in other ways buy why not this way?
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#49Earlier quoted context omitted.
This is about the Web USB API, not the entire web in general. Are you routinely granting web pages access to your USB devices? That's not a permission that web apps get by default (unlike with native desktop apps btw). It comes down to this: if you ever found yourself in a situation where you needed to connect a USB device to a remote service, would you prefer to download that service's unsandboxed native code to you…
>if you ever found yourself in a situation where you needed to connect a USB device to a remote service I have never found myself in that situation. That sounds like a really silly idea.
For those that _do_ require [such use cases][1] though; they can now do so without needing to expose their system to an unsandboxed native app.
Re: Chrome lets hackers phish even 'Unphishable' Yubikey users
#50Earlier quoted context omitted.
>if you ever found yourself in a situation where you needed to connect a USB device to a remote service I have never found myself in that situation. That sounds like a really silly idea.
Then click "deny", or (in the case of a native app) refuse to install the executable. Either way you're safe. For those that _do_ require [such use cases][1] though; they can now do so without needing to expose their system to an unsandboxed native app. [1]: https://wicg.github.io/webusb/#motivating-applications
The web is a disaster and WebUSB is a prime piece of evidence supporting this.