A chain of flaws lets a malicious Twitch chat message turn into native code execution on a streamer’s Windows PC when OBS Studio 32.2.2 or older is used with default settings. A custom Twitch chat overlay inserted viewer messages as unsanitized HTML, creating an XSS vector that allowed attacker-controlled JavaScript to run inside OBS’s embedded Chromium renderer (CEF). Because OBS bundled an outdated Chromium (127) with a known V8 type-confusion vulnerability (CVE-2024-7971) and had the Chromium sandbox disabled, JavaScript exploitation of V8 escalated directly to native code execution without requiring a separate sandbox escape. Orange reproduced the full chain, developed a proof-of-concept exploit, coordinated with the overlay developer, and reported the issue to OBS.
OBS is upgrading its embedded browser to CEF/Chromium 128+ and testing re-enabling the Chromium sandbox; fixes were merged into obs-browser and obs-studio in September. Until updated builds are widely available, streamers and overlay developers must treat Browser Source content as untrusted: insert viewer messages as plain text, sanitize any HTML, and avoid loading attacker-controlled pages into Browser Sources or docks. The CVE is known to have been exploited in the wild and appears in CISA’s catalog, making prompt remediation and cautious configuration essential.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.