安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
51 
举报此帖
https://psteamcommunity.yuanyoumao.com/groups/steamworks/announcements/detail/524229329545071275
You could go to the cve website and look up that spec, but the finer details are only revealed to security professionals.
I got that email from unity yesterday.
And for Steam to please provide more clarity on how their patch is actually protecting Steam users, and to what extent.
- What about games that are no longer "shipping", but remain in a users library?
- How do we know if an exploit exists until we unsuccessfully attempt to run it?
- Do we now need to launch every game in our library?
- Should we be taking that risk without clarity that Steam's client patch update can successfully detect when an exploit exists 100%?
- What about games that are no longer supported or being updated by the developer?
- As paying users, do we just lose out on money spent if the game has or is somehow being exploited and no longer being supported by the developer?
These are all legitimate questions that we currently have no clarity about from Steam.
Key Facts:
There is no evidence of any exploitation of the vulnerability nor has there been any impact on users or customers.
Unity has worked in close collaboration with our platform partners who have taken further steps to secure their platforms and protect end users.
Released games or applications using Unity 2017.1 or later for Windows, Android, macOS, or Linux may contain this vulnerability.
Unity has released an update for each of the major and minor versions of the Unity Editor starting with Unity 2019.1.
Unity has released a binary patcher to patch already-built applications dating back to 2017.1.
Nonetheless, it looks to me like business as usual for titles that have no active devs what-so-ever: what's there now is what you will have later. (Isn't there a similar issue with early CoD games on PC?)
So a way you'd exploit this through steam would be something like:
1. Get the target to put your malicious code somewhere predictable, like e.g. tricking them into downloading virus.dll into their download folder
2. Give them a steam:// link that runs a vulnerable unity game with the arguments, so something like:
"steam://run/[vulnerableunitygameid]//-maliciousarg path/to/virus.dll"
3. When they launch the game through that link, the game will run your code.
Steam now looks for urls containing a (potentially) malicious argument and just doesn't launch the game.
Some games might need to update more than others if e.g. they rely on adding ways to launch the game outside steam, but yes, a lot of games won't get patched, which is why the steam update should help a bit.
The exploit is that there are certain command lines you can pass to a Unity game that will load a DLL from anywhere on your system, for example your downloads folder.
Steam already warns you if you try to start a game with a custom command line via the steam://run protocol. In addition to that, it now completely blocks any attempt to start a game with any of the four broken commands in unpatched Unity games.
You're not in danger at all unless you give someone the ability to both put files on your computer and start games on your computer with custom command lines. On Android, it's more dangerous because the equivalent of steam://run is part of the operating system and not specific to one program.
Simply put, Steam, you can and should do better.
(eg : steam://rungameid/xxxxxxx)