Earlier today a 2017/2018 source code for Valve’s Source Engine was supposedly leaked online; prompting fears that this could lead to security vulnerabilities in games like Team Fortress 2 and Counter-Strike: Global Offensive. Valve confirmed that the code appears to be a repost of a 2018 “limited CS:GO engine code depot” leak and it should not be a threat to Valve’s multiplayer games. [widget path="global/article/imagegallery" parameters="albumSlug=igns-top-25-modern-pc-games&captions=true"] In a statement to IGN Valve said, “We have reviewed the leaked code and believe it to be a reposting of a limited CS: GO engine code depot released to partners in late 2017, and originally leaked in 2018.” Valved added, “From this review, we have not found any reason for players to be alarmed or avoid the current builds (as always, playing on the official servers is recommended for greatest security). We will continue to investigate the situation and will update news outlets and players if we find anything to prove otherwise. In the meantime, if anyone has more information about the leak, the Valve security page describes how best to report that information.” [ignvideo url="https://www.ign.com/videos/2014/06/19/team-fortress-2-love-and-war-cinematic"] The Twitter account @SteamDB posted this morning that the Source code for CS: GO and Team Fortress 2 dated 2017/2018 was leaked to the public today. Players online began worrying about potential security vulnerabilities the leak could open up, and users urged others to avoid Valve multiplayer games out of precaution. Despite some posts on social media, attacks on either CS: GO or Team Fortress 2 haven’t been verified, and Valve’s statement seems to suggest that there is no vulnerability in either game presently. At least on Valve’s official game servers. Developing... [poilib element="accentDivider"] Matt Kim is a reporter for IGN. If you know anything about the leak send tips to newstips@ign.com
source https://www.ign.com/articles/valve-counter-strike-source-code-leak-no-danger
No comments:
Post a Comment