[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Steam Weak File Permissions Privilege Escalation



Steam Weak File Permissions Privilege Escalation

Vendor Website : http://store.steampowered.com/

 INDEX
---------------------------------------
    
    1. CVE
    2. Background
    3. Description
    4. Impact
    5. Affected Products
    6. Solution
    7. Credit
    8. Disclosure Timeline


1. CVE
---------------------------------------
    CVE: 2015-7985


2. BACKGROUND
---------------------------------------
    Valve is the creator of Steam, the pioneering game platform that distributes and manages thousands of games directly to a community of more than 65 million players around the world.


3. DESCRIPTION
---------------------------------------

    A privilege escalation vulnerability has been identified in that the Steam Microsoft Windows client software is installed with weak default permissions. These permissions grant read and write access to the Windows Users group for the install folder. This includes Steam.exe which is launched upon user login.


4. IMPACT
---------------------------------------
    A low privileged user could modify the steam.exe binary and obtain code execution with elevated privileges upon an administrator login or execution of steam.exe

  
5. AFFECTED PRODUCTS
---------------------------------------
    Only the following versions have been confirmed vulnerable:    

    Steam 2.10.91.91


6. SOLUTION
---------------------------------------
    A workaround for the steam install folder includes removing write privileges from the Windows Users group. Additionally the vendor has provided security resources here: https://support.steampowered.com/kb_article.php?ref=1266-OAFV-8478


7. CREDIT
---------------------------------------
    The vulnerability was discovered by Andrew Smith of Sword & Shield Enterprise Security.


8. DISCLOSURE TIMELINE
---------------------------------------
    10-20-2015 - Vulnerability Discovered
    10-26-2015 - Vendor Informed
    10-26-2015 - Vendor Confirmed Receipt of Report
    10-27-2015 - CVE Requested
    10-28-2015 - Vendor Confirmed Public Disclosure
    11-12-2015 - Public Disclosure