__________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Capability ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN Vulnerability in DirectShow Could Allow Remote Code Execution [Microsoft Security Bulletin MS05-050 (904706)] October 11, 2005 21:00 GMT Number Q-011 [REVISED 18 Oct 2005] [REVISED 20 Oct 2005] [REVISED 21 Oct 2005] [REVISED 14 Dec 2005] ______________________________________________________________________________ PROBLEM: A remote code execution vulnerability exists in DirectShow that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system. PLATFORM: • Microsoft DirectX 7.0 on Microsoft Windows 2000 with Service Pack 4 • Microsoft DirectX 8.1 on Microsoft Windows XP Service Pack 1 and Microsoft DirectX 9.0c on Microsoft Windows XP with Service Pack 2 • Microsoft DirectX 9.0c on Microsoft Windows XP Professional x64 Edition • Microsoft DirectX 8.1 on Microsoft Windows Server 2003 and Microsoft DirectX 9.0c on Microsoft Windows Server 2003 with Service Pack 1 • Microsoft DirectX 8.1 on Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft DirectX 9.0c on Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems • Microsoft DirectX 9.0c on Microsoft Windows Server 2003 x64 Edition • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems. Affected Components: • Microsoft DirectX 8.0, 8.0a, 8.1, 8.1a, 8.1b, and 8.2 when installed on Windows 2000 Service Pack 4 • Microsoft DirectX 9.0, 9.0a, 9.0b, and 9.0c when installed on Windows 2000 Service Pack 4 • Microsoft DirectX 9.0, 9.0a, 9.0b, and 9.0c when installed on Windows XP Service Pack 1 • Microsoft DirectX 9.0, 9.0a, 9.0b, and 9.0c when installed on Windows Server 2003 DAMAGE: If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. SOLUTION: Apply current patches. ______________________________________________________________________________ VULNERABILITY The risk is HIGH. Could allow an attacker to take complete ASSESSMENT: control of the affected system. ______________________________________________________________________________ LINKS: CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/q-011.shtml ORIGINAL BULLETIN: http://www.microsoft.com/technet/security/Bulletin/ MS05-050.mspx CVE: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name= CVE-2005-2128 ______________________________________________________________________________ REVISION HISTORY: 10/18/2005 - revised Q-011 to reflect the changes Microsoft has made to MS05-050 where they updated it to provide additional clarity around DirectX versions in the "Affected Software" section. 10/20/2005 - revised to reflect the changes Microsoft has made to MS05-050 where they updated the Caveats and FAQ section and the What updates does this release replace. 10/21/2005 - revised to reflect the changes Microsoft has made to MS05-050 where they revised the file version under the FAQ security section. 12/14/2005 - revised to reflect the changes Microsoft has made to MS05-050 where they are advising customers that a revised version of the security update is available for Windows 2000 SP4, Windows XP SP1 and Windows 2003 listed in the "Affected Software" section. [***** Start MS05-050 *****] Microsoft Security Bulletin MS05-050 Vulnerability in DirectShow Could Allow Remote Code Execution (904706) Published: October 11, 2005 | Updated: October 21, 2005 Version: 2.0 Summary Who should read this document: Customers who use Microsoft Windows Impact of Vulnerability: Remote Code Execution Maximum Severity Rating: Critical Recommendation: Customers should apply the update immediately. Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list. Caveats: Microsoft Knowledge Base Article 909596 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 909596. Tested Software and Security Update Download Locations: Affected Software: Tested Software and Security Update Download Locations: Affected Software: • Microsoft DirectX 7.0 on Microsoft Windows 2000 with Service Pack 4 – Download the update • Microsoft DirectX 8.1 on Microsoft Windows XP Service Pack 1 and Microsoft DirectX 9.0c on Microsoft Windows XP with Service Pack 2 – Download the update • Microsoft DirectX 9.0c on Microsoft Windows XP Professional x64 Edition – Download the update • Microsoft DirectX 8.1 on Microsoft Windows Server 2003 and Microsoft DirectX 9.0c on Microsoft Windows Server 2003 with Service Pack 1 – Download the update • Microsoft DirectX 8.1 on Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft DirectX 9.0c on Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems – Download the update • Microsoft DirectX 9.0c on Microsoft Windows Server 2003 x64 Edition – Download the update • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems. Tested Microsoft Windows Components: Affected Components: • Microsoft DirectX 8.0, 8.0a, 8.1, 8.1a, 8.1b, and 8.2 when installed on Windows 2000 Service Pack 4 – Download the update • Microsoft DirectX 9.0, 9.0a, 9.0b, and 9.0c when installed on Windows 2000 Service Pack 4 – Download the update • Microsoft DirectX 9.0, 9.0a, 9.0b, and 9.0c when installed on Windows XP Service Pack 1 – Download the update • Microsoft DirectX 9.0, 9.0a, 9.0b, and 9.0c when installed on Windows Server 2003– Download the update The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site. Top of sectionTop of section General Information Executive Summary Executive Summary: This update resolves a newly-discovered, privately-reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. We recommend that customers apply the update immediately. Vulnerability Details DirectShow Vulnerability - CAN-2005-2128 A remote code execution vulnerability exists in DirectShow that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system. Mitigating Factors for DirectShow Vulnerability - CAN-2005-2128: • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Top of sectionTop of section Acknowledgments Microsoft thanks the following for working with us to help protect customers: • eEye Digital Security for reporting the DirectShow Vulnerability - CAN-2005-2128. Obtaining Other Security Updates: Updates for other security issues are available at the following locations: • Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." • Updates for consumer platforms are available at the Microsoft Update Web site. Support: • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site. Security Resources: • The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. • Microsoft Software Update Services • Microsoft Windows Server Update Services • Microsoft Baseline Security Analyzer (MBSA) • Windows Update • Microsoft Update • Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166. • Office Update Software Update Services: By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional. For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site. Windows Server Update Services: By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems. For more information about how to deploy security updates by using Windows Server Update Services, visit the Windows Server Update Services Web site. Systems Management Server: Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site. Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates. Disclaimer: The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. Revisions: • V1.0 (October 11, 2005): Bulletin published. • V1.1 (October 12, 2005): Bulletin updated to provide additional clarity around DirectX versions in the “Affected Software” section. • V1.2 (October 19, 2005): Bulleitn updated for the following: Caveats and FAQ were updated to reflect the available Microsoft Knowledge Base Article 909596 and to clarify a known issue that affected Windows 2000 SP4 customers who were running DirectX. In the Frequently asked questions (FAQ) related to this security update" section, updated the "What updates does this release replace" question to make it clearer with regards to DirectX and Windows 2000. Added information about Windows XP Professional x64 Edition to the "File Information" section under "Windows XP (all versions)". Revised the "DirectX Standalone" "Registry Key Verification" for all versions. • V1.3 (October 21, 2005): Bulletin updated to revise file version under the "Frequesntly asked questions (FAQ) related to this security update" section for "I've installed the DirectX (KB904706) security Update, what version of quartz.dll should I have installed?" DirectX Windows 2000 Service pack 4 versions 7.0 and 9.0. • V1.4 (November 8, 2005): Bulletin updated the following: Microsoft has also been made aware that when installing the "Security Update for DirectX 8.1 for Windows XP Service Pack 1” or "Security Update for DirectX 8.1 for Windows 2003" package on a computer that has DirectX 9; the install completes successfully without giving any indication that the computer was not updated. Users running DirectX 9 will still be vulnerable to the issue discussed within MS05-050 until they apply the appropriate package for their DirectX version. In "Frequently asked questions (FAQ) related to this security update" section, updated the "How can I determine whether I am running an updated version of DirectX on my system?" for Windows 2000 SP4 Multi-User Interface (MUI) users. • V2.0 (December 13, 2005): Bulletin updated to advise customers that a revised version of the security update is available for Windows 2000 SP4, Windows XP SP1 and Windows 2003, listed in the “Affected Software” section. Customers that have applied the appropriate version of DirectX on the appropriate version of Windows need not take any action. Customers that may have installed the incorrect DirectX package manually are encouraged to evaluate their systems and re-deploy the correct update to ensure that the correct version of DirectX has been updated. For additional information, see “Why did Microsoft update this bulletin on November 9, 2005.” in "Frequently asked questions (FAQ) related to this security update" section. [***** End MS05-050 *****] _______________________________________________________________________________ CIAC wishes to acknowledge the contributions of Microsoft for the information contained in this bulletin. _______________________________________________________________________________ CIAC, the Computer Incident Advisory Capability, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. CIAC services are available to DOE, DOE contractors, and the NIH. CIAC can be contacted at: Voice: +1 925-422-8193 (7x24) FAX: +1 925-423-8002 STU-III: +1 925-423-2604 E-mail: ciac@ciac.org Previous CIAC notices, anti-virus software, and other information are available from the CIAC Computer Security Archive. World Wide Web: http://www.ciac.org/ Anonymous FTP: ftp.ciac.org PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing communities receive CIAC bulletins. If you are not part of these communities, please contact your agency's response team to report incidents. Your agency's team will coordinate with CIAC. The Forum of Incident Response and Security Teams (FIRST) is a world-wide organization. A list of FIRST member organizations and their constituencies can be obtained via WWW at http://www.first.org/. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC) Q-002: 'apachetop' Insecure Temporary File Q-003: Symantec AV Scan Engine Web Interface Vulnerability Q-004: 'arc' Insecure Temporary File Creation Q-005: Updated Kernel Packages for Red Hat Linux 4 Update 2 Q-006: Tcpdump Q-007: OpenSSL Potential SSL 2.0 Rollback Q-008: Security Vulnerability Involving the umount(8) Utility Q-009: Vulnerabilities in MSDTC and COM+ Q-010: Vulnerability in the Microsoft Collaboration Data Objects