- cross-posted to:
- technology@beehaw.org
- technology
- google@lemdro.id
- cross-posted to:
- technology@beehaw.org
- technology
- google@lemdro.id
Summary
-
Researchers at the University of Wisconsin–Madison have demonstrated that Chrome browser extensions can steal passwords from text input fields, even if the extension is compliant with Chrome’s latest security and privacy standard, Manifest V3.
-
They created a proof-of-concept browser extension that could steal passwords and put it through the Chrome Web Store review process.
-
The attack works by exploiting the fact that extensions have full and unfettered access to the Document Object Model (DOM) of every web page you visit. The DOM is a representation of a web page in computer memory that can be accessed and changed, allowing the page to be modified on-the-fly.
-
The researchers found that most of the top 10,000 websites are vulnerable to this attack, including Google, Facebook, Gmail, Cloudflare, and Amazon.
-
They also analyzed the extensions already on the Chrome Web Store and found that 12.5% of them had the necessary permissions to exploit the password input field vulnerabilities.
-
The researchers offer two potential fixes: A “bolt on” remedy for vulnerable sites and a “built in” remedy for browsers.
-
The bolt on is a JavaScript library that can be added to websites to prevent unwanted access to password fields.
-
The built in remedy suggests changing Chrome to alert users whenever any JavaScript function accesses any password fields.
Possible Takeaways / Other Details
-
Google have improved security in the Manifest V3 standard, but it’s still possible to sneak in a password stealing extension into the webstore.
-
Some/all of the standard’s security improvements may have also been adopted by Microsoft Edge, and Mozilla Firefox.
-
It is important to be aware of the risks associated with using browsers’ extensions. Only install extensions from trusted sources and carefully review the permissions that they request.
They only require permission to write to the password field, they don’t necessarily need to read passwords. Although it does change the work flow for some users.
Many password managers use a “save new” or “update” login credentials feature that watches for newly used passwords and asks if you’d like to save the credentials used.
That’s going to go away if you remove the read access. That said, maybe that’s not such a bad thing. Plenty of people will dislike losing that feature, however.
And it could work how it does on Android or similar where the browser has suggestions you can select to fill the field. Originally was for accessibility but it also works for password manger suggestions or any other sutofill. The extension would offer the suggestions to the browser and only the browser would read and actually do the input.
I’m actually game for that idea, it would also make the browser responsible for parsing the many formats of html people use for structuring their input fields.