__________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Capability ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN Microsoft Security Update for Microsoft Windows [MS04-011] April 13, 2004 19:00 GMT Number O-114 [REVISED 22 Apr 2004] [REVISED 3 May 2004] [REVISED 5 May 2004] [REVISED 25 Jun 2004] ______________________________________________________________________________ PROBLEM: Microsoft has released a security update for several Windows Operating Systems. There are several vulnerabilities for remote code execution, privilege execution, and denial of service. PLATFORM: Microsoft Windows NT® Workstation 4.0 Service Pack 6a Microsoft Windows NT Server 4.0 Service Pack 6a Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6 Microsoft Windows 2000 Service Pack 2 Microsoft Windows 2000 Service Pack 3 Microsoft Windows 2000 Service Pack 4 Microsoft Windows XP Microsoft Windows XP Service Pack 1 Microsoft Windows XP 64-Bit Edition Service Pack 1 Microsoft Windows XP 64-Bit Edition Version 2003 Microsoft Windows Server™ 2003 Microsoft Windows Server 2003 64-Bit Edition Microsoft NetMeeting Microsoft Windows 98 Microsoft Windows 98 Second Edition (SE) Microsoft Windows Millennium Edition (ME) – Review the FAQ section of Microsoft's bulletin for details about these operating systems. DAMAGE: An attacker could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. SOLUTION: Apply the update immediately. ______________________________________________________________________________ VULNERABILITY The risk is HIGH. An attacker can take complete control of the ASSESSMENT: affected system. ______________________________________________________________________________ LINKS: CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/o-114.shtml ORIGINAL BULLETIN: http://www.microsoft.com/technet/security/bulletin/ ms04-011.mspx ADDITIONAL LINKS: ISS - for Network Sensor 7.0, Proventia A, G, and M http://xforce.iss.net/xforce/alerts/id/177 CVE/CAN: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name= CAN-2003-0533 CAN-2003-0663 CAN-2003-0719 CAN-2003-0806 CAN-2003-0906 CAN-2003-0907 CAN-2003-0908 CAN-2003-0909 CAN-2003-0910 CAN-2004-0117 CAN-2004-0118 CAN-2004-0119 CAN-2004-0120 CAN-2004-0123 ______________________________________________________________________________ REVISION HISTORY: 04/22/2004 - Updated O-114 to reflect the updates to Microsoft Security Bulletin MS04-11 in the following sections: Security Update Replacement, Workarounds for Utility Manager Vulnerability CAN-2003-0908, and the FAQ section. 05/03/2004 - Updated O-114 to reflect the update to Microsoft Security Bulletin MS04-11 in the Caveats section. 05/05/2004 - Updated O-114 to reflect the update to Microsoft Security Bulletin MS04-11 in the Workarounds section for the LSASS Vulnerability. 06/25/2004 - Added link to ISS Alert #177 for XPU 22.25, XPU 22.19, XPU 1.17, and XPU 1.23 updates for their Network Sensor 7.0, and Proventia A, G, and M products for the cross-site scripting and PCT vulnerabilities. [***** Start MS04-011 *****] Microsoft Security Bulletin MS04-011 Security Update for Microsoft Windows (835732) Issued: April 13, 2004 Updated: May 4, 2004 Version: 1.3 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 several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list. Caveats: The security update for Windows NT Server 4.0 Terminal Server Edition Service Pack 6 requires, as a prerequisite, the Windows NT Server 4.0 Terminal Server Edition Security Rollup Package (SRP). To download the SRP, visit the following Web site. You must install the SRP before you install the security update that is provided in this security bulletin. If you are not using Windows NT Server 4.0 Terminal Server Edition Service Pack 6 you do not need to install the SRP. Microsoft Knowledge Base Article 835732 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 835732. Tested Software and Security Update Download Locations: Affected Software: • Microsoft Windows NT® Workstation 4.0 Service Pack 6a – Download the update • Microsoft Windows NT Server 4.0 Service Pack 6a – Download the update • Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6 – Download the update • Microsoft Windows 2000 Service Pack 2, Microsoft Windows 2000 Service Pack 3, and Microsoft Windows 2000 Service Pack 4 – Download the update • Microsoft Windows XP and Microsoft Windows XP Service Pack 1 – Download the update • Microsoft Windows XP 64-Bit Edition Service Pack 1 – Download the update • Microsoft Windows XP 64-Bit Edition Version 2003 – Download the update • Microsoft Windows Server™ 2003 – Download the update • Microsoft Windows Server 2003 64-Bit Edition – Download the update • Microsoft NetMeeting • 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. The software that is listed above has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site. Top of section General Information Technical Details Executive Summary: This update resolves several newly-discovered vulnerabilities. Each vulnerability is documented in this bulletin in its own section. An attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. Microsoft recommends that customers apply the update immediately. Vulnerability Identifiers Impact of Vulnerability Windows 98, 98 SE, ME Windows NT 4.0 Windows 2000 Windows XP Windows Server 2003 LSASS Vulnerability - CAN-2003-0533 Remote Code Execution None None Critical Critical Low LDAP Vulnerability – CAN-2003-0663 Denial Of Service None None Important None None PCT Vulnerability - CAN-2003-0719 Remote Code Execution None Critical Critical Important Low Winlogon Vulnerability - CAN-2003-0806 Remote Code Execution None Moderate Moderate Moderate None Metafile Vulnerability - CAN-2003-0906 Remote Code Execution None Critical Critical Critical None Help and Support Center Vulnerability - CAN-2003-0907 Remote Code Execution None None None Critical Critical Utility Manager Vulnerability - CAN-2003-0908 Privilege Elevation None None Important None None Windows Management Vulnerability - CAN-2003-0909 Privilege Elevation None None None Important None Local Descriptor Table Vulnerability - CAN-2003-0910 Privilege Elevation None Important Important None None H.323 Vulnerability* - CAN-2004-0117 Remote Code Execution Not Critical None Important Important Important Virtual DOS Machine Vulnerability - CAN-2004-0118 Privilege Elevation None Important Important None None Negotiate SSP Vulnerability - CAN-2004-0119 Remote Code Execution None None Critical Critical Critical SSL Vulnerability - CAN-2004-0120 Denial Of Service None None Important Important Important ASN.1 “Double Free” Vulnerability - CAN-2004-0123 Remote Code Execution Not Critical Critical Critical Critical Critical Aggregate Severity of All Vulnerabilities Not Critical Critical Critical Critical Critical *Note The severity rating of H.323 Vulnerability - CAN-2004-0117 is Important for the standalone version of NetMeeting. To download an updated version of NetMeeting that addresses this vulnerability, visit the following Web site. This version of NetMeeting can be installed on all systems that are running Windows 98, Windows 98 Second Edition, Windows Millennium Edition, and Windows NT 4.0. The updated version of NetMeeting that addresses this vulnerability is version 3.01 (4.4.3399). The above assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them. Top of section Frequently asked questions (FAQ) related to this security update Why does this update address several reported security vulnerabilities? This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that contain almost identical files, customers can install only this update. What updates does this release replace? This security update replaces several prior security bulletins. The security bulletin IDs and operating systems that are affected are listed in the table below. Bulletin ID Windows NT 4.0 Windows 2000 Windows XP Windows Server 2003 MS99-023 Replaced Not Applicable Not Applicable Not Applicable MS00-027 Not Replaced Replaced Not Applicable Not Applicable MS00-032 Not Applicable Replaced Not Applicable Not Applicable MS00-070 Not Replaced Replaced Not Applicable Not Applicable MS02-050 Replaced Not Replaced Not Replaced Not Applicable MS02-051 Not Applicable Replaced Not Replaced Not Applicable MS02-071 Replaced Replaced Not Replaced Not Applicable MS03-007 Not Replaced Replaced Not Replaced Not Applicable MS03-013 Replaced Replaced Not Replaced Not Applicable MS03-025 Not Applicable Replaced Not Applicable Not Applicable MS03-041 Replaced Not Replaced Not Replaced Not Replaced MS03-045 Replaced Replaced Not Replaced Not Replaced MS04-007 Replaced Replaced Replaced Replaced Is this update a Cumulative Security Update or a Security Update Roll-up? Neither. A Cumulative Security Update would typically include support for all prior updates. This update does not include support for all prior updates on all operating systems. A Security Update Roll-up is typically used to combine previous releases into a single update to allow for easier installation and faster download. Security Update Roll-ups typically do not include modifications to address new vulnerabilities; this update does. How does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems? Microsoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site. For more information about severity ratings, visit the following Web site. Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by any of the vulnerabilities that are addressed in this security bulletin? No. None of these vulnerabilities are critical in severity on Windows 98, on Windows 98 Second Edition, or on Windows Millennium Edition. Does this update contain any other changes to functionality? Yes. In addition to the changes that are listed in each of the vulnerability details sections of this bulletin, this update includes the following change in functionality: files that end with the file name extension “.folder” are no longer associated with a directory. Files that have this extension are still supported by the affected operating system. However, those files will no longer appear as a directory in Windows Explorer and in other programs. Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required? Yes. MBSA will determine if this update is required. However, MBSA does not currently support the stand-alone version of NetMeeting for detection. MBSA will not offer the required update to the stand-alone version of NetMeeting if it has been installed on Windows NT 4.0 systems. To download the updated stand-alone version of NetMeeting that addresses the H.323 Vulnerability (CAN-2004-0117), visit the following Web site. MBSA does detect if the update for the H.323 Vulnerability (CAN-2004-0117) is required for the version of NetMeeting that shipped as part of Windows 2000, Windows XP, or Windows Server 2003. For more information about the H.323 Vulnerability (CAN-2004-0117), see that vulnerability details section of this bulletin. For more information about MBSA, visit the MBSA Web site. For more information about MBSA detection limitations, see Microsoft Knowledge Base Article 306460. How did this change from the initial release of the bulletin? When the bulletin was released on April 13, 2004, MBSA detection for this security update was disabled for Windows NT 4.0 because of the lack of detection support for the stand-alone version of NetMeeting that is described earlier in this bulletin. This changed on April 21, 2004. MBSA will now detect if this security update is required for Windows NT 4.0 even though this limitation exists. Can I use Systems Management Server (SMS) to determine if this update is required? Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to the stand-alone version of NetMeeting. Can I use Systems Management Server (SMS) to determine if the stand-alone version of NetMeeting has been installed on Windows NT 4.0 systems? Yes. SMS can help detect if the updated stand-alone version of NetMeeting is required for Windows NT 4.0 systems. SMS can search for the presence of the file “Conf.exe.” All versions before version 3.01 (4.4.3399) should be updated. Top of section Vulnerability Details LSASS Vulnerability - CAN-2003-0533: LDAP Vulnerability - CAN-2003-0663: PCT Vulnerability - CAN-2003-0719: Winlogon Vulnerability - CAN-2003-0806: Metafile Vulnerability - CAN-2003-0906: Help and Support Center Vulnerability - CAN-2003-0907: Utility Manager Vulnerability - CAN-2003-0908: A privilege elevation vulnerability exists in the way that Utility Manager launches applications. A logged-on user could force Utility Manager to start an application with system privileges and take complete control of the system. Mitigating Factors for Utility Manager Vulnerability - CAN-2003-0908: • An attacker must have valid logon credentials to exploit the vulnerability. The vulnerability could not be exploited by anonymous users. • Windows NT 4.0, Windows XP, and Windows Server 2003 are not affected by this vulnerability. Windows NT 4.0 does not implement the Utility Manager. • The Windows 2000 Hardening Guide recommends disabling the Utility Manger service. Environments that comply with these guidelines could be at a reduced risk from this vulnerability. Top of section Workarounds for Utility Manager Vulnerability - CAN-2003-0908: Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below. • Use Group Policies to disable the Utility Manager on all affected systems that do not require this feature. Because the Utility Manager is a possible attack vector, disable it using Group Policies. The Utility Manager process name is Utilman.exe. The following guide provides information about how to require users to run only approved applications using Group Policies. Note You may also review the Windows 2000 Hardening Guide. This guide includes information about how to disable the Utility Manager. Impact of Workaround: The Utility Manager provides easy access to many of the accessibility features of the operating system. This access would be unavailable until the restrictions are removed. To find information about how to manually start many of the accessibility features, visit this Web site. Top of section FAQ for Utility Manager Vulnerability - CAN-2003-0908: What is the scope of the vulnerability? This is a privilege elevation vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. What causes the vulnerability? The process used by Utility Manager to launch applications. It is possible that Utility Manager could launch applications with system privileges. What is Utility Manager? Utility Manager is an accessibility utility that allows users to check the status of accessibility programs such as Microsoft Magnifier, Narrator, or On-Screen Keyboard, and to start or stop them. What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. Who could exploit the vulnerability? An attacker must be able to log on to the system and then, after starting Utility Manager, run a program that sends a specially crafted message to Utility Manager to attempt to exploit the vulnerability. How could an attacker exploit this vulnerability? To exploit this vulnerability, an attacker would first have to start Utility Manager on Windows 2000 and then run a specially designed application that could exploit the vulnerability. In default configurations of Window 2000, Utility Manager is installed but is not running. This vulnerability could allow an attacker to gain complete control over a Windows 2000 system. What systems are primarily at risk from the vulnerability? Only Windows 2000 is affected by this vulnerability. Workstations and terminal servers that are based on Windows 2000 are primarily at risk. Servers are only at risk if users who do not have sufficient administrative credentials are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this. I am using Windows 2000, but I am not using Utility Manager or any of the accessibility features. Am I still vulnerable? Yes. By default, Utility Manager is installed and enabled. However, Utility Manager is not running by default. Could the vulnerability be exploited over the Internet? No. An attacker must be able to log on to the specific system targeted for attack. An attacker cannot load and run a program remotely using this vulnerability. What does the update do? This update removes the vulnerability by modifying the way that Utility Manager launches applications. Windows Management Vulnerability - CAN-2003-0909 Local Descriptor Table Vulnerability - CAN-2003-0910 H.323 Vulnerability - CAN-2004-0117 Virtual DOS Machine Vulnerability - CAN-2004-0118: Negotiate SSP Vulnerability - CAN-2004-0119 SSL Vulnerability - CAN-2004-0120: ASN.1 “Double Free” Vulnerability - CAN-2004-0123 Top of section Security Update Information Installation Platforms and Prerequisites: For information about the specific security update for your platform, click the appropriate link: Windows Server 2003 (all versions) Windows XP (all versions) Windows 2000 (all versions) Windows NT 4.0 (all versions) Top of section Acknowledgments Microsoft thanks the following for working with us to help protect customers: • Carlos Sarraute of Core Security Technologies for reporting the LDAP Vulnerability (CAN-2003-0663). • Internet Security Systems for reporting the PCT Vulnerability (CAN-2003-0719). • Ondrej Sevecek for reporting the Winlogon Vulnerability (CAN-2003-0806). • iDefense and Jouko Pynnönen for reporting the Help and Support Vulnerability (CAN-2003-0907). • Brett Moore of Security-Assessment.com, Cesar Cerrudo, and Ben Pryor for reporting the Utility Manager Vulnerability (CAN-2003-0908). • Erik Kamphuis of LogicaCMG working on behalf of the Dutch Tax Office for reporting the Windows Management Vulnerability (CAN-2003-0909). • NSFOCUS Security Team for reporting the Negotiate SSP Vulnerability (CAN-2004-0119). • John Lampe of Tenable Network Security for reporting the SSL Vulnerability (CAN-2004-0120) • Foundstone Labs and Qualys for reporting the ASN.1 “Double Free” Vulnerability (CAN-2004-0123). • eEye Digital Security for reporting the LSASS Vulnerability (CAN-2003-0533), Metafile Vulnerability (CAN-2003-0906), Local Descriptor Table Vulnerability (CAN-2003-0910), and the Virtual DOS Machine Vulnerability (CAN-2004-0118) Obtaining other security updates: Updates for other security issues are available from the following locations: • Security updates are available from the Microsoft Download Center: you can find them most easily by doing a keyword search for “security_patch”. • Updates for consumer platforms are available from the Windows Update Web site. Support: • Customers in the U.S. and Canada can get 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 get support from their local Microsoft subsidiaries. There is no charge for support associated with security updates. For more information on 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 Baseline Security Analyzer (MBSA) • Windows Update • Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166. • Office Update Software Update Services (SUS): Microsoft Software Update Services (SUS) enables administrators to quickly and reliably deploy the latest critical updates and security updates to Windows® 2000 and Windows Server™ 2003-based servers, as well as to desktop systems running Windows 2000 Professional or Windows XP Professional. For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. Systems Management Server (SMS): Systems Management Server can provide assistance deploying this security update. For information about Systems Management Server visit the SMS Web Site. For detailed information about the many enhancements to the security update deployment process that SMS 2003 provides, please visit the SMS 2003 Security Patch Management Web site. For users of SMS 2.0, it also provides several additional tools to assist administrators in the deployment of security updates such as the SMS 2.0 Software Update Services Feature Pack and the SMS 2.0 Administration Feature Pack. The SMS 2.0 Software Update Services Feature Pack utilizes the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin remediation. Some software updates may require administrative rights following a restart of the computer Note The inventory capabilities of the SMS 2.0 Software Update Services Feature Pack may be used for targeting updates to specific computers, and the SMS 2.0 Administration Feature Pack's Elevated Rights Deployment Tool can be used for installation. This provides optimal deployment for updates that require explicit targeting using Systems Management Server and administrative rights after the computer has been restarted. 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 April 13, 2004: Bulletin published • V1.1 April 21, 2004: Bulletin updated to reflect updated information in the Update Replacement Section. Bulletin has also been updated to reflect the change in the MBSA detection behavior as described in the updated FAQ section. The bulletin also contains revisions to the workaround section for the Utility Manager Vulnerability (CAN-2003-0908). • V1.3 May 4, 2004: Added new information in the Workarounds section for the LSASS Vulnerability. [***** End MS04-011 *****] _______________________________________________________________________________ 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) O-104: ICQ Parsing in ISS Products May Lead to Buffer Overflow O-105: Multiple Vulnerabilities in Ethereal 0.10.2 O-106: Mozilla 1.4 Vulnerabilities O-107: vfte Buffer Overflow Vulnerabilities O-108: Squid ACL Bypass Vulnerability O-109: Heimdal Kerberos Cross-Realm Vulnerability O-110: MAC OS X Jaguar and Panther Security Vulnerabilities o-111: CISCO WLSE and HSE Contain Default Passwords O-112: Cisco IPSec VPN Services Module Malformed IKE Packet Vulnerability O-113: Debian tcpdump Denial of Service