Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS07-061 - Critical

Vulnerability in Windows URI Handling Could Allow Remote Code Execution (943460)

Published: November 13, 2007 | Updated: January 16, 2008

Version: 1.2

General Information

Executive Summary

This update resolves a publicly reported vulnerability. A remote code execution vulnerability exists in the way that the Windows shell handles specially crafted URIs that are passed to it. If the Windows shell did not sufficiently validate these URIs, an attacker could exploit this vulnerability and execute arbitrary code. Microsoft has only identified ways to exploit this vulnerability on systems using Internet Explorer 7. However, the vulnerability exists in a Windows file, Shell32.dll, which is included in all supported editions of Windows XP and Windows Server 2003.

This is a critical security update for all supported editions of Windows XP and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

This security update addresses the vulnerability by changing the way that Windows shell handles invalid URIs. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

This security update also addresses the vulnerability first described in Microsoft Security Advisory 943521. For more information, see the FAQ subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update immediately.

Known Issues. Microsoft Knowledge Base Article 943460 documents currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Operating SystemMaximum Security ImpactAggregate Severity RatingBulletins Replaced by This Update
Windows XP Service Pack 2 Remote Code ExecutionCritical MS06-045
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Remote Code ExecutionCritical MS06-045
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Remote Code ExecutionCritical MS06-045
Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 Remote Code ExecutionCritical MS06-045
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems Remote Code ExecutionCritical MS06-045

Non-Affected Software

Operating System
Microsoft Windows 2000 Service Pack 4
Windows Vista
Windows Vista x64

What updates does this release replace?
This update replaces the update provided by MS06-045. This update does not replace the update provided by bulletin MS07-006 because the files that are updated in that bulletin do not replace all the files that are replaced by the update offered in bulletin MS06-045. Customers should install the updates offered from bulletins MS07-061 and MS07-006.

I am using an older version of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin have been tested to determine which versions or editions are affected. Other versions or editions are past their support life cycle. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions or editions of the software to migrate to supported versions or editions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older software 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 Microsoft Worldwide Information, 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.

Vulnerability Information

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareWindows URI Handling Vulnerability - CVE-2007-3896Aggregate Severity Rating
Windows XP Service Pack 2 Critical 

Remote Code Execution

Critical 
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Critical 

Remote Code Execution

Critical 
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Critical 

Remote Code Execution

Critical 
Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 Critical 

Remote Code Execution

Critical 
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based systems Critical 

Remote Code Execution

Critical 

A remote code execution vulnerability exists in the way that the Windows shell handles specially crafted URIs that are passed to it. An attacker could exploit this vulnerability by including a specially crafted URI in an application or attachment, which could potentially allow remote code execution.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-3896.

Mitigating Factors for Windows URI Handling Vulnerability - CVE-2007-3896

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • Windows 2000 Service Pack 4 is not affected
  • Windows Vista is not affected
  • Windows Vista x64 Edition is not affected
  • Microsoft has not identified a way to exploit this vulnerability on any Windows operating system that is running Internet Explorer 6
  • 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.
  • In an e-mail based attack of this exploit, customers who read e-mail in plain text are at less risk from this vulnerability. To be more at risk from this vulnerability, users would have to either click on a link that would take them to a malicious Web site or open an attachment.

Workarounds for Windows URI Handling Vulnerability - CVE-2007-3896

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Windows URI Handling Vulnerability - CVE-2007-3896

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged on user.

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? 
The Windows shell insufficiently handles invalid URIs.

What is a URI?
A Uniform Resource Identifier (URI) is a string of characters used to act on or identify resources from the Internet or over a network. A URL is a typical example of a URI that references a resource such as a Web site. For more information about URIs, see RFC 2396.

What might an attacker use the vulnerability to do? 
An attacker who has convinced a user to open an attachment in mail or to follow a link to an attacker's Web site could run arbitrary code as the logged on 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.

How could an attacker exploit the vulnerability? 
An attacker would have to create a specially crafted URI and provide the URI as input to an application on an affected system, which would then attempt to access the resource referred to it by the URI. Applications that take URIs as input from untrusted sources such as attachments in e-mail, documents, or data from the network assuming it will be safe, are exposed to this vulnerability. Under specific circumstances, processing specially crafted URI input could allow arbitrary code to be executed. In order to exploit the vulnerability, an attacker would have to convince the user to launch the attachment or application, or visit the Web site. An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then convince a user to view the Web site. This vulnerability might also be exploited by compromised Web sites or Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted URIs that could exploit this vulnerability. It could also be possible to display specially crafted URIs by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability? 
Systems running supported editions of Windows XP and Windows Server 2003 with Internet Explorer 7 installed are vulnerable.

What does the update do? 
The update removes the vulnerability by changing the way that the Windows shell handles invalid URIs.

I do not have Windows Internet Explorer 7 installed. Why am I receiving this update? 
The vulnerability exists in a Windows file, Shell32.dll, included in supported editions of Windows XP and Windows Server 2003. Microsoft has not identified any way to exploit this vulnerability on systems using Internet Explorer 6, which is the browser that is included with these operating systems. As a defense-in-depth measure, this security update is made available to all customers using supported editions of Windows XP and Windows Server 2003, regardless of which version of Internet Explorer is installed.

I am using Windows Vista , am I at risk from this vulnerability? 
No. Windows Vista is not affected by this vulnerability. Windows Internet Explorer 7 is included with Windows Vista but the Windows shell in Windows Vista is not affected by this vulnerability.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued. It has been assigned the Common Vulnerability and Exposure number CVE-2007-3896. This vulnerability was first described in Microsoft Security Advisory 943521.

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-2007-3896.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA 2.0.1
Windows XP Service Pack 2 Yes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2Yes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Yes
Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2Yes
Windows Server 2003 with SP1 for Itanium based systems and Windows Server 2003 with SP2 for Itanium based systems Yes

For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can 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 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

SoftwareSMS 2.0SMS 2003
Windows XP Service Pack 2 YesYes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2NoYes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 YesYes
Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2NoYes
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based systems NoYes

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionWindows XP Service Pack 2:
Windowsxp-kb943460-x86-enu /quiet
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:

WindowsServer2003.WindowsXP-kb943460-x64-enu /quiet

Installing without restartingWindows XP Service Pack 2:
Windowsxp-kb943460-x86-enu /norestart
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:

Windowsserver2003.WindowsXP-kb943460-x64-enu /norestart

Update log fileWindows XP Service Pack 2:
KB943460.log
Further informationSee the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingNot applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB943460$\Spuninst folder
File Information See the subsection, File Information.
Registry Key Verification For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB943460\Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB943460\Filelist

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.

For all supported 32-bit editions of Windows XP:

File NameVersionDateTimeSizeFolder
shell32.dll6.0.2900.324126-Oct-200710:368,454,656SP2GDR
xpsp3res.dll5.1.2600.324329-Jun-200719:26115,712SP2GDR
shell32.dll6.0.2900.324126-Oct-200710:348,460,288SP2QFE
xpsp3res.dll5.1.2600.324329-Oct-200719:04350,720SP2QFE

For all supported x64-based editions of Windows XP Professional:

File NameVersionDateTimeSizeCPUFolder
shell32.dll6.0.3790.303308-Nov-200716:5010,501,632X64SP1GDR
wshell32.dll6.0.3790.303308-Nov-200716:518,383,488X86SP1GDR\wow
shell32.dll6.0.3790.303308-Nov-200716:5110,504,704X64SP1QFE
w03a2409.dll5.2.3790.295708-Nov-200716:5129,184X64SP1QFE
wshell32.dll6.0.3790.303308-Nov-200716:518,385,536X86SP1QFE\wow
ww03a2409.dll5.2.3790.295708-Nov-200716:5128,672X86SP1QFE\wow
shell32.dll6.0.3790.418408-Nov-200716:5510,508,288X64SP2GDR
wshell32.dll6.0.3790.418408-Nov-200716:558,360,448X86SP2GDR\wow
shell32.dll6.0.3790.418408-Nov-200716:4810,508,288X64SP2QFE
wshell32.dll6.0.3790.418408-Nov-200716:488,360,448X86SP2QFE\wow

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/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

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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. 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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB943460-x86-enu /quiet
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB943460-ia64-enu /quiet
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB943460-x64-enu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB943460-x86-enu /norestart
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB943460-ia64-enu /norestart
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB943460-x64-enu /norestart
Update log fileKB943460.log
Further informationSee the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingThis security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal Information For all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB943460$\Spuninst folder
File Information See the heading, File Information.
Registry Key Verification For all supported 32-bit editions, Itanium-based editions, and x64-based editions of Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB943460\Filelist

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.

For all supported 32-bit editions of Windows Server 2003:

File NameVersionDateTimeSizeFolder
shell32.dll6.0.3790.303326-Oct-200712:518,383,488SP1GDR
shell32.dll6.0.3790.303326-Oct-200712:458,385,536SP1QFE
w03a2409.dll5.2.3790.295718-Jun-200710:3128,672SP1QFE
shell32.dll6.0.3790.418407-Nov-200721:498,360,448SP2GDR
shell32.dll6.0.3790.418407-Nov-200721:368,360,448SP2QFE

For all supported Itanium-based editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
shell32.dll6.0.3790.303308-Nov-200716:3013,237,248IA-64SP1GDR
wshell32.dll6.0.3790.303308-Nov-200716:308,383,488X86SP1GDR\wow
shell32.dll6.0.3790.303308-Nov-200716:3013,241,856IA-64SP1QFE
w03a2409.dll5.2.3790.295708-Nov-200716:3027,648IA-64SP1QFE
wshell32.dll6.0.3790.303308-Nov-200716:308,385,536X86SP1QFE\wow
ww03a2409.dll5.2.3790.295708-Nov-200716:3028,672X86SP1QFE\wow
shell32.dll6.0.3790.418408-Nov-200716:3613,244,416IA-64SP2GDR
wshell32.dll6.0.3790.418408-Nov-200716:368,360,448X86SP2GDR\wow
shell32.dll6.0.3790.418408-Nov-200716:1913,244,416IA-64SP2QFE
wshell32.dll6.0.3790.418408-Nov-200716:198,360,448X86SP2QFE\wow

For all supported x64-based editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
shell32.dll6.0.3790.303308-Nov-200716:5010,501,632X64SP1GDR
wshell32.dll6.0.3790.303308-Nov-200716:518,383,488X86SP1GDR\wow
shell32.dll6.0.3790.303308-Nov-200716:5110,504,704X64SP1QFE
w03a2409.dll5.2.3790.295708-Nov-200716:5129,184X64SP1QFE
wshell32.dll6.0.3790.303308-Nov-200716:518,385,536X86SP1QFE\wow
ww03a2409.dll5.2.3790.295708-Nov-200716:5128,672X86SP1QFE\wow
shell32.dll6.0.3790.418408-Nov-200716:5510,508,288X64SP2GDR
wshell32.dll6.0.3790.418408-Nov-200716:558,360,448X86SP2GDR\wow
shell32.dll6.0.3790.418408-Nov-200716:4810,508,288X64SP2QFE
wshell32.dll6.0.3790.418408-Nov-200716:488,360,448X86SP2QFE\wow

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/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

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 may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. 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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

  • Jesper Johansson for working with us on the Windows URI Handling Vulnerability (CVE-2007-3896).
  • Carsten H. Eiram of Secunia for working with us on the Windows URI Handling Vulnerability (CVE-2007-3896).
  • Aviv Raff of Finjan for working with us on the Windows URI Handling Vulnerability (CVE-2007-3896).
  • Petko Petkov of GNUCITIZEN for working with us on the Windows URI Handling Vulnerability (CVE-2007-3896).

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.

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 (November 13, 2007): Bulletin published.
  • V1.1 (November 21, 2007): Bulletin updated to clarify that this bulletin only replaces MS06-045 and does not replace MS07-006.
  • V1.2 (January 16, 2008): Bulletin updated to add KB article information to the Known Issues area of the General Information section.

Built at 2014-04-18T13:49:36Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.