‹ BackHN Continuity

Thread

How one Twitch chat message became code execution on a streamer’s PC

67 points · 30 comments · tau255

  1. superkuh · · focus · HN ↗
    This shouldn't be a problem right? Javascript is by default allowed to execute on your PC in every modern browser. The days where people did not blindly execute arbitrary code from unknown and random sources are far in the past. Now if you don't do that you are considered weird and no websites actually display anything when you attempt to view them.

    This is not a bug. This is the the entire design architecture's intent for modern JS application execution based "web". If this was the correct choice for the web then this should not be a problem at all. But we all know it is. The architecture choice forces this. Until we stop arbitrarily executing random third party code this will always happen. And the consequences will get worse and worse as more bare metal features are exposed in to browsers JS virtual machines.

    Be the change in the world you want to see. Turn javascript off. Use real native applications that cannot change underneath you.

    1. pie_flavor · · focus · HN ↗
      OBS explicitly disabled the security feature that would have prevented this attack in a real browser.
      1. landr0id · · focus · HN ↗
        While problematic, this is pointing the finger at the wrong thing. The version of the browser was from 2024. The permutations of full chain exploits permitting sandbox escape since then is probably pretty high.

        It's a patch gap, plain and simple. Removing the sandbox certainly did not help things.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.