Thread

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

67 points · 30 comments · tau255

superkuh · 1790470684 · 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. doodlesdev · 1790471183 · focus · HN ↗
  Craziest thing is the mixture of:
  - A browser engine outdated by two years, with known-exploited CVEs
  - Chromium sandboxing completely disabled [0]
  - JavaScript V8 Engine with JIT enabled [0]
  For me, it's surprising we haven't seen more of these yet.
  [0]: <a href="https://github.com/obsproject/obs-browser/blob/f555da02b1d5910008958ca377e0f1a3889eb023/obs-browser-plugin.cpp" rel="nofollow">https://github.com/obsproject/obs-browser/blob/f555da02b1d59...
  1. hulitu · 1790496273 · focus · HN ↗
    ... and trying hard to parse any stream of bits thrown at it. That's why iMessage and Whatsapp zero click ecploits work so well.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.