6 comments

  • taylorfinley 26 minutes 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 19 minutes ago
      Instant vote of confidence, yes!
  • ByteOfWood 7 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.
  • afavour 7 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.
  • SoftTalker 32 minutes 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.
  • ethersteeds 13 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

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