Microsoft Security Bulletin MS06-001 - Critical
Vulnerability in Graphics Rendering Engine Could Allow Remote Code Execution (912919)
Published: January 05, 2006
Version: 1.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: None
Tested Software and Security Update Download Locations:
Affected Software:
Microsoft Windows 2000 Service Pack 4 - Download the update
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 - Download the update
Microsoft Windows XP Professional x64 Edition - Download the update
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 - Download the update
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems - Download the update
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.
Note The security updates for Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 x64 Edition also apply to Microsoft Windows Server 2003 R2.
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.
General Information
Executive Summary
Executive Summary:
This update resolves a newly-discovered, public vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.
Note This vulnerability is currently being exploited and was previously discussed by Microsoft in Microsoft Security Advisory 912840.
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.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 98, Windows 98 SE, and Windows ME | Windows 2000 | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 |
|---|---|---|---|---|---|---|---|
| Graphics Rendering Engine Vulnerability - CVE-2005-4560 | Remote Code Execution\ | Not Critical | Critical | Critical | Critical | Critical | Critical |
This 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.
Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
- The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
- The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
- The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
- The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
Frequently asked questions (FAQ) related to this security update
Does this update contain any security-related changes to functionality?
Yes. The change introduced to address this vulnerability removes the support for the SETABORTPROC record type from the META_ESCAPE record in a WMF image. This update does not remove support for ABORTPROC functions registered by application SetAbortProc() API calls.
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?
For these versions of Windows, 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 one or more of the vulnerabilities that are addressed in this security bulletin?
No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical because an exploitable attack vector has not been identified that would yield a Critical severity rating for these versions. For more information about severity ratings, visit the following Web site.
Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I’m still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
Customers who require additional support for Windows NT 4.0 Service Pack 6a and Windows 2000 Service Pack 3 must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.
For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.
Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.
The Security Update Inventory Tool can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.
The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, see the following Microsoft Web site.
For more information about SMS, visit the SMS Web site.
Vulnerability Details
Graphics Rendering Engine Vulnerability - CVE-2005-4560:
A remote code execution vulnerability exists in the Graphics Rendering Engine because of the way that it handles Windows Metafile (WMF) images. An attacker could exploit the vulnerability by constructing a specially crafted WMF image that could potentially allow remote code execution if a user visited a malicious Web site or opened a specially crafted attachment in e-mail. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
Mitigating Factors for Graphics Rendering Engine Vulnerability - CVE-2005-4560:
- In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. Also, Web sites that accept or host user-provided content or advertisements, and compromised Web sites, may contain malicious content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail or Instant Messenger request that takes users to the attacker's Web site.
- 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.
Workarounds for Graphics Rendering Engine Vulnerability - CVE-2005-4560:
Microsoft has tested the following workaround. While this workaround will not correct the underlying vulnerability, it will help block known attack vectors.
Unregister the Windows Picture and Fax Viewer (Shimgvw.dll) on Windows XP Service Pack 1; Windows XP Service Pack 2; Windows Server 2003 and Windows Server 2003 Service Pack 1
Microsoft has tested the following workaround. While this workaround will not correct the underlying vulnerability, it helps block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
Note This workaround is intended to help protect against Web based exploit vectors and is not effective against exploits that have Windows Metafile images embedded in Word documents and other similar attack vectors.
Note The following steps require Administrative privileges. We recommend that you restart the computer after you apply this workaround. Alternatively, you can log out and log back in after you apply the workaround. However, we do recommend that you restart the computer.
To un-register Shimgvw.dll, follow these steps:
- Click Start, click Run, type "regsvr32 -u %windir%\system32\shimgvw.dll" (without the quotation marks), and then click OK.
- When a dialog box appears that confirms that the process has been successful, click OK.
Impact of Workaround: The Windows Picture and Fax Viewer will no longer start when users click a link to an image type that is associated with the Windows Picture and Fax Viewer.
To undo this workaround after the security update has been deployed, reregister Shimgvw.dll. To do this, use this same procedure, but replace the text in step 1 with “regsvr32 %windir%\system32\shimgvw.dll” (without the quotation marks).
FAQ for Graphics Rendering Engine Vulnerability - CVE-2005-4560:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. 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.
What causes the vulnerability?
A vulnerability exists in the way that the Graphics Rendering Engine handles specially crafted WMF images that could allow arbitrary code to be executed.
What is the Windows Metafile (WMF) image format?
A Windows Metafile (WMF) image is a 16-bit metafile format that can contain both vector information and bitmap information. It is optimized for the Windows operating system.
For more information about image types and formats, see Microsoft Knowledge Base Article 320314 or visit the MSDN Library Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by creating a malicious Web page or a specially crafted attachment in e-mail and then persuading the user to visit the page or open the attachment. If the user visited the page or opened the attachment, the attacker could cause malicious code to run in the security context of the locally logged on user. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.
An attacker could also attempt to exploit this vulnerability by embedding a specially crafted Windows Metafile (WMF) image within other files such as Word documents and convince a user to open this document.
What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and reading e-mail or visiting Web sites for any malicious action to occur. Therefore, any systems where e-mail is read or where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to read e-mail or to visit Web sites, such as most server systems, are at a reduced risk.
Does this vulnerability affect image formats other than Windows Metafile (WMF)?
The only image format that is affected is the Windows Metafile (WMF) format. It is possible, however, that an attacker could rename the file name extension of a WMF file to that of a different image format. In this situation, it is likely that the Graphics Rendering Engine would detect and render the file as a WMF image, which could allow exploitation.
If I block files that use the .wmf file name extension, can this protect me against attempts to exploit this vulnerability?
No. The Graphics Rendering Engine does not determine file types by the file name extensions that they use. Therefore, if an attacker alters the file name extension of a WMF file, the Graphics Rendering Engine could still render the file in a way that could exploit the vulnerability.
Does the workaround in this bulletin protect me from attempts to exploit this vulnerability through WMF images with changed extensions?
Yes. The workaround in this bulletin help protect against WMF images with changed extensions. This workaround is only effective in scenarios where the Windows Picture and Fax Viewer (Shimgvw.dll) would have been opened. This workaround is intended to help protect against Web based exploit vectors and is not effective against exploits that have Windows Metafile images embedded in Word documents and other similar attack vectors.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
No. Although Windows Millennium Edition does contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following Web site.
What does the update do?
The update removes the vulnerability by modifying the way that Windows Metafile (WMF) images are handled.
Specifically, the change introduced to address this vulnerability removes the support for the SETABORTPROC record type from the META_ESCAPE record in a WMF image. This update does not remove support for ABORTPROC functions registered by application SetAbortProc() API calls.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2005-4560.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.
Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2005-4560.
What’s Microsoft’s response to the availability of third party patches for the WMF vulnerability?
Microsoft recommends that customers download and deploy the security update associated with this security bulletin.
As a general rule, it is a best practice to obtain security updates for software vulnerabilities from the original vendor of the software. With Microsoft software, Microsoft carefully reviews and tests security updates to ensure that they are of high quality and have been evaluated thoroughly for application compatibility. In addition, Microsoft’s security updates are offered in 23 languages for all affected versions of the software simultaneously.
Microsoft cannot provide similar assurance for independent third party security updates.
How does this vulnerability relate to the vulnerabilities that were corrected by MS05-053?
Both vulnerabilities were in the Graphics Rendering Engine. However, this update addresses a new vulnerability that was not addressed as part of MS05-053. MS05-053 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability. This update does not replace MS05-053. You must install this update and the update that is provided as part of the MS05-053 security bulletin to help protect your system against both vulnerabilities.
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log: path | Allows the redirection of installation log files |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program |
| /ER | Enables extended error reporting |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb912919-x86-enu /quiet
Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB912919.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb912919-x86-enu /norestart
For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB912919$\Spuninst folder.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Gdi32.dll | 5.2.3790.462 | 31-Dec-2005 | 04:23 | 271,872 | RTMGDR |
| Gdi32.dll | 5.2.3790.462 | 31-Dec-2005 | 04:37 | 272,384 | RTMQFE |
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:12 | 281,600 | SP1GDR |
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:25 | 282,112 | SP1QFE |
Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Gdi32.dll | 5.2.3790.462 | 31-Dec-2005 | 04:48 | 806,912 | IA-64 | RTMGDR |
| Wgdi32.dll | 5.2.3790.462 | 31-Dec-2005 | 04:48 | 250,880 | x86 | RTMGDR\WOW |
| Gdi32.dll | 5.2.3790.462 | 31-Dec-2005 | 04:50 | 808,448 | IA-64 | RTMQFE |
| Wgdi32.dll | 5.2.3790.462 | 31-Dec-2005 | 04:50 | 251,392 | x86 | RTMQFE\WOW |
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 05:09 | 907,264 | IA-64 | SP1GDR |
| Wgdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 05:09 | 285,184 | x86 | SP1GDR\WOW |
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:50 | 907,264 | IA-64 | SP1QFE |
| Wgdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:50 | 285,184 | x86 | SP1QFE\WOW |
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 05:00 | 609,792 | x64 | SP1GDR |
| Wgdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 05:00 | 285,184 | x86 | SP1GDR\WOW |
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:46 | 609,792 | x64 | SP1QFE |
| Wgdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:46 | 285,184 | x86 | SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry key.
Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB912919\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 912919 security update into the Windows installation source files.
Windows XP (all versions)
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program |
| /ER | Enables extended error reporting |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:
Windowsxp-kb912919-x86-enu /quiet
Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB912919.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:
Windowsxp-kb912919-x86-enu /norestart
For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB912919$\Spuninst folder.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Gdi32.dll | 5.1.2600.1789 | 02-Jan-2006 | 22:38 | 260,608 | SP1QFE |
| Mf3216.dll | 5.1.2600.1331 | 30-Mar-2004 | 01:48 | 36,864 | SP1QFE |
| Gdi32.dll | 5.1.2600.2818 | 29-Dec-2005 | 02:54 | 280,064 | SP2GDR |
| Gdi32.dll | 5.1.2600.2818 | 29-Dec-2005 | 03:04 | 280,064 | SP2QFE |
Windows XP Professional x64:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 05:00 | 609,792 | x64 | SP1GDR |
| Wgdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 05:00 | 285,184 | x86 | SP1GDR\WOW |
| Gdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:46 | 609,792 | x64 | SP1QFE |
| Wgdi32.dll | 5.2.3790.2606 | 31-Dec-2005 | 04:46 | 285,184 | x86 | SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB912919\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB912919\Filelist
Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 912919 security update into the Windows installation source files.
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).
The software that is listed 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.
For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.
Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.
Installation Information
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program |
| /ER | Enables extended error reporting |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:
Windows2000-kb912919-x86-enu /quiet
Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB912919.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:
Windows2000-kb912919-x86-enu /norestart
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB912919$\Spuninst folder.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows 2000 Service Pack 4 and Small Business Server 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Gdi32.dll | 5.0.2195.7073 | 30-Dec-2005 | 16:15 | 233,744 |
| Mf3216.dll | 5.0.2195.7011 | 13-Jan-2005 | 10:09 | 37,136 |
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB912919\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 912919 security update into the Windows installation source files.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Dan Hubbard of WebSense for working with us on the Graphics Rendering Engine Vulnerability - CVE-2005-4560.
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 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 this security bulletin 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 (January 5, 2006): Bulletin published.
Built at 2014-04-18T13:49:36Z-07:00