logoalt Hacker News

Universal XSS in uBlock Origin from website-driven element picker

173 points • by zaik • today at 2:04 AM • 46 comments • view on HN

Comments

taylorfinley • today at 2:41 AM

Really love the "I wrote all the prose, gpt wrote the POC" disclaimer, I would love to see more of those kinds of signals on human authored content.

➕ show 1 reply
ByteOfWood • today at 3:00 AM

I never really loved how extensions have to put their interfaces in the website's DOM if they want to be able to work with the page's elements, like this selector, or a password manager's suggested logins. Especially in the password manager's scenario, it could leak what accounts you have to a given website to that website itself, if the page is looking for new DOM elements. Not exactly a showstopper vulnerability, but it's not a good thing.

➕ show 3 replies
forgotmypw17 • today at 3:54 AM

For those checking (I still had the vulnerable version), you should be at these versions or higher:

uBlock Origin: 1.76.4

uBO Lite: 2026.1110.1816

➕ show 1 reply
akersten • today at 3:33 AM

So this seems totally solvable by the create-rule element living in the browser chrome instead of the website DOM... why aren't we doing that?

tux • today at 3:47 AM

I recommend to delete old forefox profiles and create new once, than install new fixed uBlock0. You should always use separate profiles for all tasks with hardened user.js anyway. Don’t forget to save your bookmarks. Anynew profile creates new UUID.

SoftTalker • today at 2:35 AM

uBlock Origin has broad permission to inspect and modify anything on a page (it needs it, to do what it does). This would seem to make any vulnerability easier to exploit.

usr1106 • today at 4:02 AM

Haven't used any uBlock for many years. Use DNS based blocking.

For many years I was a happy user of CAD (Cookie Auto Delete). Unfortunately it seems unmaintained. I have now stopped to install it. Don't understand enough of modern browsers to even have an educated guess what kind of vulnerabilities could be buried in the old code.

➕ show 1 reply
ethersteeds • today at 2:54 AM

> But the attacker website can itself hook the XHR made from inside the no-fetch-if hook to extract the random extension UUID.

Oh great. I recently learned[0] that some Firefox extensions can be tricked into leaking their install-unique UUID, which can then be used as a tracking identifier. Today I learn that any site can get my unique uBO UUID by hooking fetch('/adsbygoogle.js').

That is... an ironic disaster.

[0] https://news.ycombinator.com/item?id=50454639

➕ show 1 reply
afavour • today at 2:59 AM

I understand why folks railed against web extension lock downs that blocked directly editing page content but this is a great example of why it’s a powder keg.

➕ show 1 reply
maplet • today at 3:49 AM

Good day to use EWW

TZubiri • today at 2:57 AM

Software professionals should uninstall a javascript plugin that runs on every website whose purpose is to consume content more comfortably.

➕ show 1 reply
lakhya • today at 5:02 AM

[flagged]

negura • today at 4:20 AM

The concept of browser extensions seems terrible in general. There are many that ship with malware, botnets, infostealers etc. uBlock Origin even requires a compiled .wasm module. It's unwise to grant that level of complexity from third party devs permission over something as sensitive as your web browser.

➕ show 2 replies
jeffbee • today at 3:27 AM

Manifest V3 wins again

➕ show 3 replies