|
Microsoft Security Bulletin MS08-035 – ImportantVulnerability in Active Directory Could Allow Denial of Service (953235)Published: June 10, 2008 | Updated: June 11, 2008 Version: 1.1 Executive SummaryThis
security update resolves a privately reported vulnerability in
implementations of Active Directory on Microsoft Windows 2000 Server,
Windows Server 2003, and Windows Server 2008; Active Directory
Application Mode (ADAM) when installed on Windows XP Professional and
Windows Server 2003; and Active Directory Lightweight Directory Service
(AD LDS) when installed on Windows Server 2008. The vulnerability could
be exploited to allow an attacker to cause a denial of service
condition. On Windows XP Professional, Windows Server 2003, and Windows
Server 2008, an attacker must have valid logon credentials to exploit
this vulnerability. An attacker who successfully exploited this
vulnerability could cause the system to stop responding or
automatically restart. This security update is rated Important
for all supported editions of Microsoft Windows 2000 Server, and rated
Moderate for select editions of Windows XP Professional, Windows Server
2003, and Windows Server 2008. For more information, see the
subsection, Affected and Non-Affected Software, in this section. The
security update addresses the vulnerability by validating client LDAP
requests. For more information about the vulnerability, 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 at the earliest opportunity. 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 Microsoft Windows 2000 Server Service Pack 4 | Active Directory
(KB949014) | Denial of Service | Important | MS08-003 | Windows XP Professional Service Pack 2 | ADAM
(KB949269) | Denial of Service | Moderate | MS08-003 | Windows XP Professional Service Pack 3 | ADAM
(KB949269) | Denial of Service | Moderate | None | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | ADAM
(KB949269) | Denial of Service | Moderate | MS08-003 | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Active Directory
(KB949014) | Denial of Service | Moderate | MS08-003 | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | ADAM
(KB949269) | Denial of Service | Moderate | MS08-003 | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Active Directory
(KB949014) | Denial of Service | Moderate | MS08-003 | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | ADAM
(KB949269) | Denial of Service | Moderate | MS08-003 | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Active Directory
(KB949014) | Denial of Service | Moderate | MS08-003 | Windows Server 2008 for 32-bit Systems* | Active Directory
(KB949014) | Denial of Service | Moderate | None | Windows Server 2008 for 32-bit Systems* | AD LDS
(KB949014) | Denial of Service | Moderate | None | Windows Server 2008 for x64-based Systems* | Active Directory
(KB949014) | Denial of Service | Moderate | None | Windows Server 2008 for x64-based Systems* | AD LDS
(KB949014) | Denial of Service | Moderate | None |
*For
supported editions of Windows Server 2008, the same severity rating
applies whether or not 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. Non-Affected Software Windows 2000 Professional Service Pack 4 | Windows XP Home Service Pack 2 | Windows XP Tablet Edition Service Pack 2 | Windows XP Media Center Edition Service Pack 2 | Windows Vista and Windows Vista Service Pack 1 | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Windows Server 2008 for Itanium-based Systems |
Note These editions of Windows are not affected because they do not include ADAM or the Active Directory server component.  | |
I am running one of the platforms that are listed in the affected software table. Why am I not being offered the update?
The
update will only be offered to systems on which the affected component
is both installed and enabled. Active Directory and AD LDS are enabled
by default upon installation. ADAM is not enabled upon installation. To
have ADAM enabled on your machine, you need to create an instance of
ADAM via the ADAM menu group under the Start menu. 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. | |
|
Active Directory on Microsoft Windows 2000 Server Service Pack 4 | Important
Denial of Service | Important | ADAM when installed on Windows XP Professional Service Pack 2 and Windows XP Professional Service Pack 3 | Moderate
Denial of Service | Moderate | ADAM when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Moderate
Denial of Service | Moderate | Active Directory on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Moderate
Denial of Service | Moderate | ADAM when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Moderate
Denial of Service | Moderate | Active Directory on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Moderate
Denial of Service | Moderate | ADAM when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Moderate
Denial of Service | Moderate | Active
Directory on Windows Server 2003 with SP1 for Itanium-based Systems and
Windows Server 2003 with SP2 for Itanium-based Systems | Moderate
Denial of Service | Moderate | Active Directory on Windows Server 2008 for 32-bit Systems* | Moderate
Denial of Service | Moderate | AD LDS on Windows Server 2008 for 32-bit Systems* | Moderate
Denial of Service | Moderate | Active Directory on Windows Server 2008 for x64-based Systems* | Moderate
Denial of Service | Moderate | AD LDS on Windows Server 2008 for x64-based Systems* | Moderate
Denial of Service | Moderate |
*For
supported editions of Windows Server 2008, the same severity rating
applies whether or not 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
denial of service vulnerability exists in implementations of Active
Directory on Microsoft Windows 2000 Server, Windows Server 2003, and
Windows Server 2008. The vulnerability also exists in implementations
of Active Directory Application Mode (ADAM) when installed on Windows
XP and Windows Server 2003 and Active Directory Lightweight Directory
Services (AD LDS) when installed on Windows Server 2008. The
vulnerability is due to insufficient validation of specially crafted
LDAP requests. An attacker who successfully exploited this
vulnerability could cause the computer to stop responding and
automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-1445. 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: Microsoft has not identified any mitigating factors for this vulnerability. | |
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: | • | Block TCP ports 389, 636, 3268 and 3269 at the perimeter firewall These
ports are used to initiate a connection with the affected component.
Blocking them at the enterprise firewall, both inbound and outbound,
will help prevent systems that are behind that firewall from attempts
to exploit this vulnerability. We recommend that you block all
unsolicited inbound communication from the Internet to help prevent
attacks that may use other ports. For more information about ports, see
TCP and UDP Port Assignments. |
| |
What is the scope of the vulnerability?
This
is a denial of service vulnerability. An attacker who exploited this
vulnerability could cause the affected system to stop responding and
automatically restart. Note that the denial of service vulnerability
would not allow an attacker to execute code or to elevate their user
rights, but it could cause the affected system to stop accepting
requests. What causes the vulnerability?
The LDAP service performs insufficient checks for specially crafted LDAP requests. What is LDAP?
Lightweight
Directory Access Protocol (LDAP) is an open network protocol standard
designed to provide access to distributed directories. What is Active Directory?
Active
Directory is a Windows component that provides central authentication
and authorization services for Windows-based computers. What is Active Directory Application Mode (ADAM)?
ADAM
is a Lightweight Directory Access Protocol (LDAP) directory service
that runs as a user service for Windows XP and Windows Server 2003,
rather than as a system service. What is Active Directory Lightweight Directory Service (AD LDS)?
AD LDS
is a Lightweight Directory Access Protocol (LDAP) directory service
that runs as a user service for Windows Server 2008, rather than as a
system service. What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause a user’s system to become non-responsive and restart. How could an attacker exploit the vulnerability?
An
attacker could try to exploit the vulnerability by sending a specially
crafted LDAP packet to the ADAM or an Active Directory or AD LDS
server. For Windows 2000 Server, any anonymous user with access to the
target network could deliver a specially crafted network packet to the
affected system in order to exploit this vulnerability. On Windows
Server 2003, Windows Server 2008, or systems with ADAM installed, the
attacker must have valid authentication credentials in order to exploit
this vulnerability. What systems are primarily at risk from the vulnerability?
Lightweight
Directory Access Protocol (LDAP) is a requirement for Active Directory
and ADAM. Therefore, any system running as an ADAM, Active Directory,
or AD LDS server is affected by this vulnerability. What does the update do?
The update removes the vulnerability by validating the specially crafted client LDAP requests. 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 Server Service Pack 4 | Yes | Windows XP Professional Service Pack 2 and Windows XP Professional 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 Server 2008 for 32-bit Systems | Yes | Windows Server 2008 for x64-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 Server Service Pack 4 | Yes | Yes | Yes | Yes | Windows XP Professional Service Pack 2 and Windows XP Professional 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 Server 2008 for 32-bit Systems | No | No | See Note for Windows Server 2008 below | Yes | Windows Server 2008 for x64-based Systems | No | No | See Note for 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 (SCCM) 2007 uses WSUS 3.0 for detection of
updates. For more information about SCCM 2007 Software Update
Management, visit System Center Configuration Manager 2007. Note for Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for 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. | |
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 Server Service Pack 4 with Active Directory:
Windows2000-kb949014-x86-enu /quiet | Installing without restarting | Microsoft Windows 2000 Server Service Pack 4 with Active Directory:
Windows2000-kb949014-x86-enu /norestart | Update log file | Microsoft Windows 2000 Server Service Pack 4 with Active Directory:
kb949014.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 Server Service Pack 4 with Active Directory:
Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility located in the %Windir%\$NTUninstallKB949014$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 953235 | Registry Key Verification | Microsoft Windows 2000 Server Service Pack 4 with Active Directory: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB949014\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. 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 Professional Service Pack 2 with ADAM and Windows XP Professional Service Pack 3 with ADAM:
Windowsxp-kb949269-x86-enu /quiet | | Windows XP Professional x64 Edition with ADAM and Windows XP Professional x64 Edition Service Pack 2 with ADAM:
WindowsServer2003.WindowsXP-kb949269-x64-enu /quiet | Installing without restarting | Windows XP Professional Service Pack 2 with ADAM and Windows XP Professional Service Pack 3 with ADAM:
Windowsxp-kb949269-x86-enu /norestart | | Windows XP Professional x64 Edition with ADAM and Windows XP Professional x64 Edition Service Pack 2 with ADAM:
WindowsServer2003.WindowsXP-kb949269-x64-enu /norestart | Update log file | KB949269.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%\$NTUninstallKB949269$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 953235 | Registry Key Verification | For all supported 32-bit editions of Windows XP Professional:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB949269\Filelist | | For all supported x64-based editions of Windows XP Professional:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB949269\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. 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 with Active Directory:
Windowsserver2003-kb949014-x86-enu /quiet | | For all supported x64-based editions of Windows Server 2003 with Active Directory:
Windowsserver2003.WindowsXP-KB949014-x64-enu /quiet | | For all supported Itanium-based editions of Windows Server 2003 with Active Directory:
Windowsserver2003-KB949014-ia64-enu /quiet | Installing without restarting | For all supported 32-bit editions of Windows Server 2003 with Active Directory:
Windowsserver2003-kb949014-x86-enu /norestart | | For all supported x64-based editions of Windows Server 2003 with Active Directory:
Windowsserver2003.WindowsXP-KB949014-x64-enu /norestart | | For all supported Itanium-based editions of Windows Server 2003 with Active Directory:
Windowsserver2003-KB949014-ia64-enu /norestart | Update log file | KB949014.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%\$NTUninstallKB949014$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 953235 | Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB949014\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 Server 2003 with ADAM:
Windowsserver2003-kb949269-x86-enu /quiet | | For all supported x64-based editions of Windows Server 2003 with ADAM:
Windowsserver2003.WindowsXP-KB949269-x64-enu /quiet | | For all supported Itanium-based editions of Windows Server 2003 with ADAM:
Windowsserver2003-KB949269-ia64-enu /quiet | Installing without restarting | For all supported 32-bit editions of Windows Server 2003 with ADAM:
Windowsserver2003-kb949269-x86-enu /norestart | | For all supported x64-based editions of Windows Server 2003 with ADAM:
Windowsserver2003.WindowsXP-KB949269-x64-enu /norestart | | For all supported Itanium-based editions of Windows Server 2003 with ADAM:
Windowsserver2003-KB949269-ia64-enu /norestart | Update log file | KB949269.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%\$NTUninstallKB949269$\Spuninst folder | File Information | See Microsoft Knowledge Base Article 953235 | Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB949269\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 Server 2008 with Active Directory or AD LDS:
Windows6.0-KB949014-x86 /quiet
For all supported x64-based editions of Windows Server 2008 with Active Directory or AD LDS:
Windows6.0-KB949014-x64 /quiet
| Installing without restarting | For all supported 32-bit editions of Windows Server 2008 with Active Directory or AD LDS:
Windows6.0-KB949014-x86 /quiet /norestart
For all supported x64-based editions of Windows Server 2008 with Active Directory or AD LDS:
Windows6.0-KB949014-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 953235 | 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 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 Details
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. |
|
AcknowledgmentsMicrosoft thanks the following for working with us to help protect customers: | • | Alex Matthews and John Guzik of Securify for reporting the Active Directory Vulnerability – (CVE-2008-1445) |
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 (June 10, 2008): Bulletin published. | | • | V1.1
(June 11, 2008): Removed erroneous known issues entry from the Update
FAQ. Also added ports to be blocked in the Workarounds for Active
Directory Vulnerability - CVE-2008-1445 section. |
|
