|
Microsoft Security Bulletin MS09-006 – CriticalVulnerabilities in Windows Kernel Could Allow Remote Code Execution (958690)Published: March 10, 2009 Version: 1.0 Executive SummaryThis
security update resolves several privately reported vulnerabilities in
the Windows kernel. The most serious vulnerability could allow remote
code execution if a user viewed a specially crafted EMF or WMF image
file from an affected system. This security update is rated
Critical for all supported editions of Microsoft Windows 2000, Windows
XP, Windows Server 2003, 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 validating input
passed from user mode through the kernel component of GDI, correcting
the way that the kernel validates handles, and changing the way that
the Windows kernel handles specially crafted invalid pointers. 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. The
majority of customers have automatic updating enabled and will not need
to take any action because this security update will be downloaded and
installed automatically. Customers who have not enabled automatic
updating need to check for updates and install this update manually.
For information about specific configuration options in automatic
updating, see Microsoft Knowledge Base Article 294781. For
administrators and enterprise installations, or end users who want to
install this security update manually, Microsoft recommends that
customers apply the update immediately using update management
software, or by checking for updates using the Microsoft Update service. Known Issues. None Affected and Non-Affected SoftwareThe
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 *Windows Server 2008 server core installation affected.
For supported editions of Windows Server 2008, this update applies,
with the same severity rating, whether or not Windows Server 2008 was
installed using the Server Core installation option. 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.  | |
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 958690. Are
the Windows Server 2008 Service Pack 2 Beta, Windows Vista Service Pack
2 Beta, and Windows 7 Beta releases affected by this vulnerability?
Yes.
These vulnerabilities were reported after the release of Windows Server
2008 Service Pack 2 Beta, Windows Vista Service Pack 2 Beta, and
Windows 7 Beta. Customers running these platforms are encouraged to
download and apply the update to their systems. 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." Why does this update address several reported security vulnerabilities?
This
update contains support for several vulnerabilities because the
modifications that are required to address these issues are located in
related files. Instead of having to install several updates that are
almost the same, customers need to install this update only. 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. | |
The
following severity ratings assume the potential maximum impact of the
vulnerability. For information regarding the likelihood, within 30 days
of this security bulletin's release, of the exploitability of the
vulnerability in relation to its severity rating and security impact,
please see the Exploitability Index in the March bulletin summary. For more information, see Microsoft Exploitability Index. |
Microsoft Windows 2000 Service Pack 4 | Critical
Remote Code Execution | Important
Elevation of Privilege | Important
Elevation of Privilege | Critical | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Critical
Remote Code Execution | Important
Elevation of Privilege | Important
Elevation of Privilege | Critical | Windows XP Professional x64 Edition | Critical
Remote Code Execution | Important
Elevation of Privilege | Important
Elevation of Privilege | Critical | Windows XP Professional x64 Edition Service Pack 2 | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Server 2003 Service Pack 1 | Critical
Remote Code Execution | Important
Elevation of Privilege | Important
Elevation of Privilege | Critical | Windows Server 2003 Service Pack 2 | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Server 2003 x64 Edition | Critical
Remote Code Execution | Important
Elevation of Privilege | Important
Elevation of Privilege | Critical | Windows Server 2003 x64 Edition Service Pack 2 | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Vista and Windows Vista Service Pack 1 | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Server 2008 for 32-bit Systems* | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Server 2008 for x64-based Systems* | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical | Windows Server 2008 for Itanium-based Systems | Critical
Remote Code Execution | Important
Elevation of Privilege | Not applicable | Critical |
*Windows Server 2008 server core installation affected.
For supported editions of Windows Server 2008, this update applies,
with the same severity rating, whether or not Windows Server 2008 was
installed using the Server Core installation option. 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 in the Windows kernel due to
improper validation of input passed from user mode through the kernel
component of GDI. An attacker who successfully exploited this
vulnerability could run arbitrary code in kernel mode. An attacker
could then install programs; view, change, or delete data; or create
new accounts with full user rights. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0081. 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 Web page that is used to exploit this vulnerability. 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.
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
Instant Messenger message that takes users to the attacker's Web site. |
| |
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: | • | Turn off metafile processing by modifying the registry
Customers
who have applied the security update associated with Microsoft Security
Bulletin MS07-017 or customers using Windows Vista or Windows Server
2008 can disable metafile processing by modifying the registry. This
setting will help protect the affected system from attempts to exploit
this vulnerability. To modify the 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 click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize | 3. | On the Edit menu, point to New, and then click DWORD. | 4. | Type DisableMetaFiles, and then press ENTER. | 5. | On the Edit menu, click Modify to modify the DisableMetaFiles registry entry. | 6. | In the Value data box, type 1, and then click OK. | 7. | Exit Registry Editor. | 8. | Restart the computer. |
Impact of workaround.
Turning off processing of metafiles may cause the appearance of the
output from software or system components to decrease in quality.
Turning off processing of metafiles may also cause software or system
components to fail completely. This workaround has been identified to
have a potentially significant functionality impact and should be
evaluated and tested carefully to determine its applicability. Examples include the following: | • | You cannot print on the computer. | | • | Some applications on the computer may be unable to display Clipart. | | • | Some scenarios that involve OLE rendering may break. This most often occurs when the object server is not active. |
For more information on this setting read Microsoft Knowledge Base Article 941835. How to undo the workaround. 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_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize | 3. | On the Edit menu, click Modify to modify the DisableMetaFiles registry entry. | 4. | In the Value data box, type 0, and then click OK. | 5. | Exit Registry Editor. | 6. | Restart the computer. |
You may have to restart your computer for this change to take effect. |
| |
What is the scope of the vulnerability?
This
is a remote code execution vulnerability. 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. What causes the vulnerability?
The Windows kernel does not properly validate input passed from user mode through the kernel component of GDI. What is the Windows kernel?
The
Windows kernel is the core of the operating system. It provides system
level services such as device management and memory management, it
allocates processor time to processes, and it manages error handling. What is GDI?
The
Microsoft Windows graphics device interface (GDI) enables applications
to use graphics and formatted text on both the video display and the
printer. Windows-based applications do not access the graphics hardware
directly. Instead, GDI interacts with device drivers on behalf of
applications. For more information about GDI, visit the Windows GDI Start Page. What are Windows Metafile (WMF) and Enhanced Metafile (EMF) image formats?
A
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. An EMF image is a 32-bit format that can
contain both vector information and bitmap information. This format is
an improvement over the Windows Metafile Format and contains extended
features. For more information about image types and formats, see Microsoft Knowledge Base Article 320314. Additional information about these file formats is also available at the MSDN Library Web Site. What might an attacker use the vulnerability to do?
An
attacker who successfully exploited this vulnerability could run
arbitrary code. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. How could an attacker exploit the vulnerability?
For
remote code execution, this vulnerability requires that a user view a
specially crafted image file. This vulnerability may also be exploited
by an attacker logged on to the local system. An attacker could then
run a specially crafted application that could exploit the
vulnerability and take complete control over the affected system. In
an e-mail attack scenario, an attacker could exploit the vulnerability
by sending an e-mail with a specially crafted EMF or WMF image file
embedded in it to the user and convincing the user to view or preview
the e-mail. An attacker could also embed a specially crafted EMF or WMF
image file in an Office document and convince the user to open the file. In
a Web-based attack scenario, an attacker would have to host a Web site
that contains an EMF or WMF image 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. 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 validating input passed from user mode through the kernel component of GDI. 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. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No.
Microsoft had not received any 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. | |
An
elevation of privilege vulnerability exists in the Windows kernel due
to the manner in which the kernel validates handles. An attacker who
successfully exploited this vulnerability could run arbitrary code in
kernel mode. An attacker could then install programs; view, change, or
delete data; or create new accounts with full user rights. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0082. 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: | • | An
attacker must have valid logon credentials and be able to log on
locally to a vulnerable system in order to exploit this vulnerability.
The vulnerability could not be exploited remotely or by anonymous users. |
Microsoft has not identified any workarounds for this vulnerability. | |
What is the scope of the vulnerability?
This
is an elevation of privilege vulnerability. An attacker who
successfully exploited this vulnerability could execute arbitrary code
and 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. What causes the vulnerability?
The Windows kernel does not properly validate handles when performing certain actions. What is the Windows kernel?
The
Windows kernel is the core of the operating system. It provides system
level services such as device management and memory management,
allocates processor time to processes, and manages error handling. What might an attacker use the vulnerability to do?
An
attacker who successfully exploited this vulnerability could run
arbitrary code in kernel mode. An attacker could then install programs;
view, change, or delete data; or create new accounts with full user
rights. How could an attacker exploit the vulnerability?
To
exploit this vulnerability, an attacker would first have to log on to
the system. An attacker could then run a specially crafted application
that could exploit the vulnerability and take complete control over the
affected system. 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 correcting the way that the kernel validates handles. 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. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No.
Microsoft had not received any 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. | |
An
elevation of privilege vulnerability exists in the Windows kernel due
to improper handling of a specially crafted invalid pointer. An
attacker who successfully exploited this vulnerability could run
arbitrary code in kernel mode. An attacker could then install programs;
view, change, or delete data; or create new accounts with full user
rights. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0083. 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: | • | An
attacker must have valid logon credentials and be able to log on
locally to a vulnerable system in order to exploit this vulnerability.
The vulnerability could not be exploited remotely or by anonymous users. |
Microsoft has not identified any workarounds for this vulnerability. | |
What is the scope of the vulnerability?
This
is an elevation of privilege vulnerability. An attacker who
successfully exploited this vulnerability could execute arbitrary code
and 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. What causes the vulnerability?
The Windows kernel does not properly handle specially crafted invalid pointers. What is the Windows kernel?
The
Windows kernel is the core of the operating system. It provides system
level services such as device management and memory management,
allocates processor time to processes, and manages error handling. What might an attacker use the vulnerability to do?
An
attacker who successfully exploited this vulnerability could run
arbitrary code in kernel mode. An attacker could then install programs;
view, change, or delete data; or create new accounts with full user
rights. How could an attacker exploit the vulnerability?
To
exploit this vulnerability, an attacker would first have to log on to
the system. An attacker could then run a specially crafted application
that could exploit the vulnerability and take complete control over the
affected system. 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 changing the way that the Windows kernel handles specially crafted invalid pointers. 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. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No.
Microsoft had not received any 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. | |
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. Microsoft Windows 2000 Service Pack 4 | Yes | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Yes | Windows Vista and Windows Vista Service Pack 1 | Yes | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Yes | Windows Server 2008 for 32-bit Systems | Yes | Windows Server 2008 for x64-based Systems | Yes | Windows Server 2008 for Itanium-based Systems | Yes |
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. Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes | Windows Vista and Windows Vista Service Pack 1 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes | Windows Server 2008 for 32-bit Systems | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes | Windows Server 2008 for x64-based Systems | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes | Windows Server 2008 for Itanium-based Systems | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
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: | |
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 may be included in a future update rollup | Deployment | | Installing without user intervention | Microsoft Windows 2000 Service Pack 4:
Windows2000-kb958690-x86-enu /quiet | Installing without restarting | Microsoft Windows 2000 Service Pack 4:
Windows2000-kb958690-x86-enu /norestart | Update log file | Microsoft Windows 2000 Service Pack 4:
kb958690.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | Yes, you must restart your system after you apply this security update | HotPatching | Not applicable | Removal Information | Microsoft Windows 2000 Service Pack 4:
Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility located in the %Windir%\$NTUninstallKB958690$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 958690 | Registry Key Verification | Microsoft Windows Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB958690\Filelist |
| |
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. 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 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. This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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 | Displays a dialog box prompting the local user to allow a restart. | /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. | /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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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 | Displays a dialog box prompting the local user to allow a restart. | /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 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 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 edition of the operating system, or the programs that
are installed on your system, 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 system
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. |
| |
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 intervention | Windows XP Service Pack 2 and Windows XP Service Pack 3:
Windowsxp-kb958690-x86-enu /quiet | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-kb958690-x64-enu /quiet | Installing without restarting | Windows XP Service Pack 2 and Windows XP Service Pack 3:
Windowsxp-kb958690-x86-enu /norestart | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-kb958690-x64-enu /norestart | Update log file | KB958690.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | Yes, you must restart your system after you apply this security update | HotPatching | Not applicable | Removal Information | Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility located in the %Windir%\$NTUninstallKB958690$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 958690 | Registry Key Verification | For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB958690\Filelist | | For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB958690\Filelist |
Note
For supported versions of Windows XP Professional x64 Edition, this
security update is the same as supported versions of the Windows Server
2003 x64 Edition security update. | |
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. 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 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. This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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 | Displays a dialog box prompting the local user to allow a restart. | /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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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 | Displays a dialog box prompting the local user to allow a restart. | /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 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 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 edition of the operating system, or the programs that
are installed on your system, 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 system
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. |
| |
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 intervention | For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb958690-x86-enu /quiet | | For all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-KB958690-x64-enu /quiet | | For all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-KB958690-ia64-enu /quiet | Installing without restarting | For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb958690-x86-enu /norestart | | For all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-KB958690-x64-enu /norestart | | For all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-KB958690-ia64-enu /norestart | Update log file | KB958690.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | Yes, you must restart your system after you apply this security update. | HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. | Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB958690$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 958690 | Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB958690\Filelist |
| |
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. 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 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. This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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 | Displays a dialog box prompting the local user to allow a restart. | /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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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 | Displays a dialog box prompting the local user to allow a restart. | /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 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 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 edition of the operating system, or the programs that
are installed on your system, 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 system
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. |
| |
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 intervention | For all supported 32-bit editions of Windows Vista:
Windows6.0-KB958690-x86 /quiet
For all supported x64-based editions of Windows Vista:
Windows6.0-KB958690-x64 /quiet | Installing without restarting | For all supported 32-bit editions of Windows Vista:
Windows6.0-KB958690-x86 /quiet /norestart
For all supported x64-based editions of Windows Vista:
Windows6.0-KB958690-x64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | Yes, you must restart your system after you apply this security update. | HotPatching | Not applicable. | Removal Information | WUSA.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 Information | See Microsoft Knowledge Base Article 958690 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
| |
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. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When 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. |
|
| |
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 intervention | For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB958690-x86 /quiet
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB958690-x64 /quiet
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB958690-ia64 /quiet | Installing without restarting | For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB958690-x86 /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB958690-x64 /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB958690-ia64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | Yes, you must restart your system after you apply this security update. | HotPatching | Not applicable. | Removal Information | WUSA.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 Information | See Microsoft Knowledge Base Article 958690 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
| |
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. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When 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. |
|
AcknowledgmentsMicrosoft thanks the following for working with us to help protect customers: | • | Helmut Buhler (http://home.arcor.de/clipboarder/) for reporting the Windows Kernel Input Validation Vulnerability (CVE-2009-0081) | | • | Thomas Garnier of SkyRecon for reporting the Windows Kernel Handle Validation Vulnerability (CVE-2009-0082) |
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. |
DisclaimerThe
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 (March 10, 2009): Bulletin published. |
|
