After two years, Valve has patched the critical remote code execution exploit disclosed by @floesen_ https://t.co/JLdImZVAKrApril 17, 2021
Early last week a non-profit group dedicated to software reverse-engineering publicly announced (opens in new tab) that a dangerous exploit it had found in the Steam backend had gone unfixed for nearly two years, and worse, Valve was allegedly attempting to prevent them from publicly disclosing its existence. The exploit, involving Steam Invites, allegedly allowed a hacker to gain full control of a victim's system via a remote code execution.
Members of Secret Club, the non-profit organization that found the exploit, went public on Twitter (opens in new tab) about its existence after Valve had not taken action to fix the exploit for two years since Secret Club had notified it about the problem.
White-hat hacker and software reverse-engineer communities often find exploits in software and report those discreetly to companies. They're often paid for that work through so-called "bug bounty" programs and organizations like HackerOne (opens in new tab), however in this case the bounty program was widely perceived as a shield that let the exploit go unfixed: If the good guy discloses the bug they found publicly to try and get it fixed, the reward is put at risk.
The original finder of the exploit has confirmed the fix and says Valve has provided them with permission to disclose details. They are working on a detailed technical writeup for release in the future.
Good news! Valve fixed my recent exploit and gave me permissions to disclose details. That being said, I am working on a detailed technical write-up which I am going to release soon. Stay tuned!April 17, 2021
Public concern has now moved to other alleged Source Engine exploits reported by Secret Club which have gone unfixed. These include a Team Fortress 2 community server exploit (opens in new tab) and two (opens in new tab) separate (opens in new tab) CS:GO RCE exploits.
Update: A Valve rep clarified via email that the issue was specifically with the Source Engine, and not Steam. "We made a number of updates last week to address the issue, and responded to the HackerOne report," the rep said. "We believe the issue is resolved and continue to monitor the situation."