9 comments

  • tux 1 minute ago
    I recommend to delete old browser 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. Any new profile creates new UUID.
  • ByteOfWood 48 minutes ago
    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.
    • wtallis 36 minutes ago
      Did XUL extensions in Firefox prior to WebExtensions have a different way of interacting with the page contents? I know they tended to integrate better with the host browser's UI and inherited more of the host OS's UI conventions as a result, but the web back then didn't require as many CSS-based ad blocking rules (domain/URL-based rules worked for almost everything) so I don't remember what the element picker UI was like on eg. AdBlock Plus or Adblock 0.5.
  • taylorfinley 1 hour ago
    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.
    • qn8bdebq 1 hour ago
      Instant vote of confidence, yes!
      • MOARDONGZPLZ 21 minutes ago
        I wouldn’t say that, but it’s honest. And I’ll read the write up and reserve judgement until I’m done or decide it’s not worth continuing. When AI writes the article and there’s a disclaimer, I won’t read it. Saw one the other day: I used ai to write this, if you have a problem with that, stop reading. Of course, I did stop reading (and flagged the post).
  • akersten 15 minutes ago
    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?
  • ethersteeds 54 minutes ago
    > 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

  • SoftTalker 1 hour ago
    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.
  • TZubiri 51 minutes ago
    Software professionals should uninstall a javascript plugin that runs on every website whose purpose is to consume content more comfortably.
    • xp84 26 minutes ago
      It’s not about comfort. It’s basic security at this point. 2026 web ads are cancer.
  • afavour 48 minutes ago
    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.
    • GCUMstlyHarmls 40 minutes ago
      Wonder what the over-under is on a page exploiting your `block-element` interface if you happen to open it (I guess you could sort of encourage that interaction) vs explicitly getting served malware eg "Discover-Tech’s Controlium".
  • jeffbee 21 minutes ago
    Manifest V3 wins again
    • fc417fc802 17 minutes ago
      Manifest v3 is the adblock and sanitization equivalent of encasing your computer in cement and then declaring it secure.
      • NooneAtAll5 15 minutes ago
        > encasing your computer in cement

        mafia execution?