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

Microsoft Security Bulletin MS08-075 - Critical

Vulnerabilities in Windows Search Could Allow Remote Code Execution (959349)

Published: December 09, 2008 | Updated: December 10, 2008

Version: 1.1

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Windows Search. These vulnerabilities could allow remote code execution if a user opens and saves a specially crafted saved-search file within Windows Explorer or if a user clicks a specially crafted search URL. An attacker who successfully exploited these vulnerabilities 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.

The most severe vulnerability is rated Critical for all supported editions of Windows Vista and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by modifying the way that Windows Explorer frees memory when saving Windows Search files and by modifying the way that Windows Explorer interprets parameters when parsing the search-ms protocol. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update immediately.

Known Issues. None

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 Vista and Windows Vista Service Pack 1
(KB958623)
Remote Code ExecutionImportantMS08-038
Windows Vista and Windows Vista Service Pack 1
(KB958624)
Remote Code ExecutionCriticalNone
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1
(KB958623)
Remote Code ExecutionImportantMS08-038
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1
(KB958624)
Remote Code ExecutionCriticalNone
Windows Server 2008 for 32-bit Systems*
(KB958623)
Remote Code ExecutionImportantMS08-038
Windows Server 2008 for 32-bit Systems*
(KB958624)
Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems*
(KB958623)
Remote Code ExecutionImportantMS08-038
Windows Server 2008 for x64-based Systems*
(KB958624)
Remote Code ExecutionCriticalNone
Windows Server 2008 for Itanium-based Systems
(KB958623)
Remote Code ExecutionImportantMS08-038
Windows Server 2008 for Itanium-based Systems
(KB958624)
Remote Code ExecutionCriticalNone

*Windows Server 2008 server core installation not affected. The vulnerabilities addressed by these updates do not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option, even though the files affected by these vulnerabilities may be present on the system. However, users with the affected files will still be offered this update because the update files are newer (with higher version numbers) than the files that are currently on your system. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Non-Affected Software

Operating System
Microsoft Windows 2000 Service Pack 4
Windows XP Service Pack 2
Windows XP Service Pack 3
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems

Where are the file information details? 
The file information details can be found in Microsoft Knowledge Base Article 959349.

Why does this bulletin contain two updates for each affected operating system? 
This bulletin contains two updates, identified by KB number, for each affected operating system because the modifications that are required to address the vulnerabilities are located in separate components. Customers need to install both updates for each operating system that is applicable to their environment.

I am using an older release 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 releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases 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 releases 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 Saved Search Vulnerability - CVE-2008-4268 Windows Search Parsing Vulnerability - CVE-2008-4269Aggregate Severity Rating
Windows Vista and Windows Vista Service Pack 1Important
Remote Code Execution
Critical
Remote Code Execution
Critical
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1Important
Remote Code Execution
Critical
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems*Important
Remote Code Execution
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems*Important
Remote Code Execution
Critical
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based SystemsImportant
Remote Code Execution
Critical
Remote Code Execution
Critical

*Windows Server 2008 server core installation not affected. The vulnerabilities addressed by these updates do not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option, even though the files affected by these vulnerabilities may be present on the system. However, users with the affected files will still be offered this update because the update files are newer (with higher version numbers) than the files that are currently on your system. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

A remote code execution vulnerability exists when saving a specially crafted search file within Windows Explorer. This operation causes Windows Explorer to exit and restart in an exploitable manner.

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

Mitigating Factors for Windows Saved Search Vulnerability - CVE-2008-4268

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:

  • The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open and save an attachment that is sent in an e-mail message.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a specially crafted saved-search (.search-ms) file. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Attempts to exploit this vulnerability require user interaction.
  • 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.
  • Users running Internet Explorer 7 will be prompted by a dialog box indicating a web page is attempting to open content in Windows Explorer. This dialog box prompts the user to "Allow" or "Don't Allow" the content, but also allows users to not display messages of this type again. Users who have previously selected "Do not show me the warning for this program again" for Windows Explorer will not receive this prompt.

Workarounds for Windows Saved Search Vulnerability - CVE-2008-4268

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Temporarily change the file type associated with the “.search-ms” file extension. Enter the following command at an elevated command prompt:

    assoc .search-ms=xmlfile

    Impact of workaround. Saved-search files will open as XML files in Internet Explorer.

    How to undo the workaround. Enter the following command at an elevated command prompt:

    assoc .search-ms=SearchFolder

  • Modify the registry to deny users the ability to open saved-search files or to access the saved search folder.

    To modify the registry key, follow these steps:

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate and then expand the following registry subkey:

      HKEY_CLASSES_ROOT\SearchFolder

      Click Edit, and then click Permissions

      Note Make a note of the permissions that are listed in this dialog box so that you can restore them to their original values at a later time.
    3. Click Advanced.
    4. Click to clear the Include inheritable permissions from this object's parent check box. You are prompted to click Copy, Remove, or Cancel. Click Remove, and then click OK.
    5. You receive a message that states that no one will be able to access this registry key. Click Yes, and then click OK to close the Permissions for SearchFolder dialog box.

    Impact of workaround. Users will be unable to open saved search files or access the saved search folder.

    How to undo the workaround. Restore the previously configured permissions on the registry key by clicking to check Include inheritable permissions from this object's parent and then clicking OK two times.

  • Unregister the SearchFolder file type.

    To modify the registry key, follow these steps:

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Using the Interactive Method

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate and then click the following registry subkey:

      HKEY_CLASSES_ROOT\SearchFolder
    3. Click the File menu and select Export.
    4. In the Export Registry File dialog box, enter SearchFolder_file_association_registry_backup.reg and click Save.

      Note This will create a backup of this registry key in the My Documentsfolder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    Using a Managed Deployment Script

    1. Create a backup copy of the registry keys by using a managed deployment script that contains the following commands:

      Regedit.exe /e SearchFolder_registry_backup.reg
      HKEY_CLASSES_ROOT\SearchFolder
    2. Next, save the following to a file with a .REG extension, such as Delete_SearchFolder_file_association.reg:

      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\SearchFolder]
    3. Run the above registry script on the target machine with the following command from an elevated command prompt:

      Regedit.exe /s Delete_SearchFolder_file_association.reg

    Impact of workaround. Double-clicking on a saved search folder will no longer open a window displaying the search results.

    How to undo the workaround:

    Using the Interactive Method

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select SearchFolder_file_association_registry_backup.reg and click Open.

    Using a Managed Deployment Script

    Restore the original state by running the following command:

    Regedit.exe /s SearchFolder_registry_backup.reg

FAQ for Windows Saved Search Vulnerability - CVE-2008-4268

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? 
The Windows Explorer does not correctly free memory when saving Windows Search files.

What is Windows Search? 
Windows Search is a standard component of Windows Vista and Windows Server 2008 that is enabled by default. Windows Search allows instant search capabilities for most common file and data types such as e-mail, contacts, calendar appointments, documents, photos, multimedia, and other formats extended by third parties. These capabilities enable consumers and information workers to more efficiently find, manage, and organize the increasing amount of data common in home and enterprise environments. For more information, see the Windows Search home page.

Is the Windows Search component available for Windows XP affected by this issue?
No. Although Windows Search is as optional add-in for Windows XP, it is not affected by this issue.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code on a user’s system. 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.

How could an attacker exploit the vulnerability? 
This vulnerability requires that a user open and save a specially crafted saved-search file with an affected version of Windows Explorer.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted saved-search file to the user and by convincing the user to open the file. After opening the file, the user would have to save the saved-search file in order for exploit to occur. The exploit occurs regardless of where the search is saved.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a saved-search file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. The attacker would then have to convince the user to open and save a specially crafted search files. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by modifying the way that Windows Explorer frees memory when saving Windows Search files.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A remote code execution vulnerability exists in Windows Explorer that allows an attacker to construct a malicious web page that includes a call to the search-ms protocol handler. The protocol handler in turn passes untrusted data to Windows Explorer.

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

Mitigating Factors for Windows Search Parsing Vulnerability - CVE-2008-4269

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:

  • In a Web-based attack scenario, an attacker could host a Web site that contains a specially crafted Windows Search (search-ms://) URL. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Attempts to exploit this vulnerability require user interaction.
  • 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.
  • Customers who are running Internet Explorer 7 with default settings will receive a pop-up warning asking users if they want to allow the web page to communicate with Windows Explorer. The default setting is to not allow the communication.
  • Windows Vista and Windows Server 2008 systems will display a warning dialog before executing a program from outside of the intranet. This warning will not be displayed if the attacker tries to reference and executable within the intranet or on the target’s machine.

Workarounds for Windows Search Parsing Vulnerability - CVE-2008-4269

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Disable search-ms protocol handler within Windows Explorer

    Note Repairing Office or installing an Office security update may undo this workaround.

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry before you edit it.

    To modify the registry key, follow these steps:

    Using the Interactive Method

    1. Click Start, click Run, type "regedit" (without the quotation marks) in the Open box, and then click OK.
    2. Locate and then expand the following registry subkey:
    3. HKEY_CLASSES_ROOT\search-ms\shell\open.
    4. Click on Command.
    5. Click the File menu and select Export.
    6. In the Export Registry File dialog box, enter "Search-ms_pluggable_protocol_registry_backup.reg" and click Save.
    7. Edit the (Default) registry value by double-clicking it. Clear all data from the Value data: field.
    8. Click OK.

    Using a Managed Deployment Script

    1. Create a backup copy of the registry keys by using a managed deployment script that contains the following command:

      regedit /e Search-ms_pluggable_protocol_registry_backup.reg HKEY_CLASSES_ROOT\search-ms\shell\open\command.
    2. Next, save the following to a file with a .REG extension, such as
      "Disable_search-ms_pluggable_protocol.reg":

      Windows Registry Editor Version 5.00
      [HKEY_CLASSES_ROOT\search-ms\shell\open\command]
      @=""
    3. Run the above registry script on the target machine with the following command from an elevated command prompt:

      Regedit.exe /s Disable_ search-ms_pluggable_protocol.reg

    Impact of workaround.

    Web pages will not be able to launch Windows searches.

    How to undo the workaround.

    Using the Interactive Method

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select "Search-ms_pluggable_protocol_registry_backup.reg" and click Open.

    Using a Managed Deployment Script

  • Restore the original state by running the following command:

    Regedit.exe /s Search-ms_pluggable_protocol_registry_backup.reg

FAQ for Windows Search Parsing Vulnerability - CVE-2008-4269

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? 
Windows Explorer does not correctly interpret parameters when parsing the search-ms protocol.

What is the search-ms Protocol? 
The search-ms application protocol is a convention for querying the Windows Search index. The protocol enables applications, like Microsoft Windows Explorer, to query the index with parameter-value arguments, including property arguments, previously saved searches, Advanced Query Syntax, Natural Query Syntax, and language code identifiers (LCIDs) for both the Indexer and the query itself. For more information, see the following MSDN article.

Is the Windows Search component available for Windows XP affected by this issue?
No. Although Windows Search is as optional add-in for Windows XP, it is not affected by this issue.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code on a user’s system. 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.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit the vulnerability and then convince a user to visit the Web site. The attacker could also take advantage of compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted 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 convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger message that takes users to the attacker's Web site.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The security update addresses the vulnerability by modifying the way that Windows Explorer interprets parameters when parsing the search-ms protocol.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems 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.1
Windows Vista and Windows Vista Service Pack 1Yes
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1Yes
Windows Server 2008 for 32-bit SystemsYes
Windows Server 2008 for x64-based SystemsYes
Windows Server 2008 for Itanium-based SystemsYes

For more information about MBSA 2.1, see MBSA 2.1 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. 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 with SUSFPSMS 2003 with ITMUConfiguration Manager 2007
Windows Vista and Windows Vista Service Pack 1NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for 32-bit SystemsNoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for x64-based SystemsNoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for Itanium-based SystemsNoNoSee Note for Windows Vista and Windows Server 2008 belowYes

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), 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.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

Note for Windows Vista and Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability.

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.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Affected Software

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

Windows Vista (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 PacksThe 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 Vista:
Windows6.0-KB958623-x86 /quiet

For all supported 32-bit editions of Windows Vista:
Windows6.0-KB958624-x86 /quiet

For all supported x64-based editions of Windows Vista:
Windows6.0-KB958623-x64 /quiet

For all supported x64-based editions of Windows Vista:
Windows6.0-KB958624-x64 /quiet
Installing without restartingFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB958623-x86 /quiet /norestart

For all supported 32-bit editions of Windows Vista:
Windows6.0-KB958624-x86 /quiet /norestart

For all supported x64-based editions of Windows Vista:
Windows6.0-KB958623-x64 /quiet /norestart

For all supported x64-based editions of Windows Vista:
Windows6.0-KB958624-x64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update
HotPatchingNot applicable
Removal InformationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 959349
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether 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
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (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 PacksThe 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 2008:
Windows6.0-KB958623-x86 /quiet

For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB958624-x86 /quiet

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB958623-x64 /quiet

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB958624-x64 /quiet

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB958623-ia64 /quiet

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB958624-ia64 /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB958623-x86 /quiet /norestart

For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB958624-x86 /quiet /norestart

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB958623-x64 /quiet /norestart

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB958624-x64 /quiet /norestart

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB958623-ia64 /quiet /norestart

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB958624-ia64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update
HotPatchingNot applicable
Removal InformationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 959349
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether 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
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • Andre Protas of eEye Digital Security for reporting the Windows Saved Search Vulnerability (CVE-2008-4268)
  • Nate McFeters for reporting the Windows Search Parsing Vulnerability (CVE-2008-4269)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

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 (December 9, 2008): Bulletin published.
  • V1.1 (December 10, 2008): Corrected registry key in Workarounds for Windows Search Parsing Vulnerability - CVE-2008-4269 section.

Built at 2014-04-16T02:39:51Z-07:00

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