LinkedIn silently probes for 2,953 Chrome extensions on every page load.

all 4 comments

sorted by: hot top controversial new old
[–] 11 points 9 months ago (3 children)

Does this work on firefox? Does ublock origin block this?

Is this why linkedin eats so damn much ram. It eays 300 mb for a single tab. I opened 3 linkedin tabs and it lagged my entire computer.

  • source
  • hideshow 3 child comments
  • [–] [S] 25 points 9 months ago (2 children)

    As far as I can see Firefox is not affected by this as they are using random UUIDs for extensions on each startup and this tracks Chrome package IDs that are static.

  • source
  • parent
  • hideshow 2 child comments
  • 7 comments in c/privacy@programming.dev view that post
    [–] 16 points 9 months ago (1 child)

    If I use Firefox, am I immune to this kind of privacy invasion?

  • source
  • hideshow 1 child comment
  • [–] 16 points 9 months ago

    Why the hell is this even possible? Why should a web page have access to the extensions you run?

  • source
  • [–] 5 points 9 months ago

    They couldn’t round it up to 3000? They got shy or what?

  • source
  • [–] 2 points 9 months ago (2 children)

    Uhm, doesn't really sound like this could be true. Maybe I'm missing something?

    You'd see 2953 get requests in your network tab, right?

    And the article says:

    LinkedIn silently probes for 2,953 Chrome extensions on every page load.

    Surely it would be drastically noticeable if for every page load they do 3k get requests to the chrome store

  • source
  • hideshow 2 child comments
  • [–] 20 points 9 months ago (1 child)

    Dude it asks your browser, not the chrome store.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 9 months ago

    Yea, well that was my first though, but then I though - why would chrome even allow any website to just arbitrary check which extensions you have installed.

    So I checked the scripts and at this line the script is showing

    async function fetchExtensionInfo(extensionId) {
      return new Promise((resolve) => {
        const url = `https://chromewebstore.google.com/detail/$%7BextensionId%7D`;
    

    So I thought maybe they were calling the chromewebstore foreach plugin, and if you have an extension already installed, you get a different response than when you don't - or something.

    But I suppose I'm wrong and for some reason a site can just ask the browser internally which plugins are installed

  • source
  • parent