Beware of the new features of Chrome WebUSB and WebBluetooth: Browsers use more and more APIs for more functionality.
But this is not always good.
Two recent additions to Chrome, with the WebUSB and WebBluetooth APIs, allow sites to interact with devices connected to the computer running the browser.
This can be very useful, but sometimes the addition of new features has unpredictable consequences.
WebUSB and WebBluetooth APIs, for example, leave vulnerabilities that allow for highly sophisticated phishing attacks. These attacks could bypass two-factor authentication devices that use USB ports, such as the Yubikey device.
Security researchers have recently shown that Chrome browser WebUSB functionality can also be used to communicate directly with two-factor authentication devices, not just the Google U2F API.
The attack bypasses any protection offered by two-factor identity devices.
Chrome prompts you when it encounters a page that is trying to use the WebUSB or WebBluetooth API. The user must allow the login request and type or paste the username and password of the account on the page he wants to log in.
Users should pay attention to the dialogues that appear and ask for permissions. Websites designed for attacks could provide assurances and prompts that the rights they request are necessary for better functionality of the external device.
The two add-ons block APIs in the browser.
So if you don't use WebUSB and WebBluetooth features, these extensions are a temporary solution until Google fixes security issues.