|
Microsoft Security Bulletin MS08-003 – ImportantVulnerability in Active Directory Could Allow Denial of Service (946538)Published: February 12, 2008 | Updated: March 26, 2008 Version: 1.2 Executive SummaryThis
important security update resolves a privately reported vulnerability
in implementations of Active Directory on Microsoft Windows 2000 Server
and Windows Server 2003 and Active Directory Application Mode (ADAM)
when installed on Windows XP and Windows Server 2003. The vulnerability
could allow a denial of service condition. On Windows Server 2003 and
Windows XP 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 is an important security update for
all supported editions of Microsoft Windows 2000, and a moderate
security update for Windows XP, and Windows Server 2003. For more
information, see the subsection, Affected and Non-Affected Software, in this section. This
security update addresses the vulnerability by 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. Microsoft Knowledge Base Article 946538
documents the currently known issues that customers may experience when
they install this security update. The article also documents
recommended solutions for these issues. 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
(KB943484) | Denial of Service | Important | MS07-039 | Windows XP Professional Service Pack 2 | ADAM
(KB931374) | Denial of Service | Moderate | None | Windows XP Professional x64 Edition and Windows XP Professional Edition Service Pack 2 | ADAM
(KB931374) | Denial of Service | Moderate | None | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Active Directory
(KB943484) | Denial of Service | Moderate | MS07-039 | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | ADAM
(KB931374) | Denial of Service | Moderate | None | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Active Directory
(KB943484) | Denial of Service | Moderate | MS07-039 | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | ADAM
(KB931374) | Denial of Service | Moderate | None | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Active Directory
(KB943484) | Denial of Service | Moderate | MS07-039 |
Non-Affected Software Windows Vista | Windows Vista Service Pack 1 (all editions) | Windows Vista x64 Edition | Windows Server 2008 (all editions) | Windows XP Home Service Pack 2 | Windows XP Tablet Edition Service Pack 2 | Windows XP Media Center Edition Service Pack 2 | Windows 2000 Professional Service Pack 4 |
Note: These editions of Windows are not affected because they do not include ADAM or the Active Directory server component.  | |
What is the known issue that customers may experience when installing this security update?
Microsoft
is aware of LDAP queries which may fail when trying to display very
large lists of mailboxes in the Exchange Management console of
Microsoft Exchange Server. For more information about this issue see
the known issues section of the Microsoft Knowledge Base Article 946538. I am using an older version of the software discussed in this security bulletin. What should I do?
The
affected software listed in this bulletin have been tested to determine
which versions or editions are affected. Other versions or editions are
past their support life cycle. To determine the support life cycle for
your software version or edition, visit Microsoft Support Lifecycle. It
should be a priority for customers who have older versions or editions
of the software to migrate to supported versions or editions to prevent
potential exposure to vulnerabilities. For more information about the
Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services. Customers
who require custom support for older software must contact their
Microsoft account team representative, their Technical Account Manager,
or the appropriate Microsoft partner representative for custom support
options. Customers without an Alliance, Premier, or Authorized Contract
can contact their local Microsoft sales office. For contact
information, visit Microsoft Worldwide Information, select the country, and then click Go
to see a list of telephone numbers. When you call, ask to speak with
the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ. | |
|
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 | Moderate
Denial of Service | Moderate | ADAM Windows XP Professional x64 Edition and Windows XP Professional 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 200 with SP2 for Itanium-based Systems | Moderate
Denial of Service | Moderate |
| |
A
denial of service vulnerability exists in implementations of Active
Directory on Microsoft Windows 2000 and Windows Server 2003. The
vulnerability also exists in implementations of Active Directory
Application Mode (ADAM) when installed on Windows XP and Windows Server
2003. The vulnerability is due to improper 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-0088. 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 and 3268 at the perimeter firewall These
ports are used to initiate a connection with the affected component.
Blocking it 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 the TCP and
UDP Port Assignments Web site. | | • | To
help protect from network-based attempts to exploit this vulnerability,
block the affected ports by using IPSec on the affected systems. Use
Internet Protocol security (IPSec) to help protect network
communications. Detailed information about IPSec and about how to apply
filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878. |
| |
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 Active Directory?
The
main purpose of Active Directory is to provide 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, 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 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 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 or Active Directory
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 computers in your organization. For more
information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update." Finally, security updates can be downloaded from the Microsoft Update Catalog.
The Microsoft Update Catalog provides a searchable catalog of content
made available through Windows Update and Microsoft Update, including
security updates, drivers and service packs. By searching using the
security bulletin number (such as, “MS07-036”), you can add all of the
applicable updates to your basket (including different languages for an
update), and download to the folder of your choosing. For more
information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ. Detection and Deployment Guidance Microsoft
has provided detection and deployment guidance for this month’s
security updates. This guidance will also help IT professionals
understand how they can use various tools to help deploy the security
update, such as Windows Update, Microsoft Update, Office Update, the
Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool,
Microsoft Systems Management Server (SMS), and the Extended Security
Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723. Microsoft Baseline Security Analyzer Microsoft
Baseline Security Analyzer (MBSA) allows administrators to scan local
and remote systems for missing security updates as well as common
security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer. The following table provides the MBSA detection summary for this security update. Microsoft Windows 2000 Service Pack 4 | 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 |
For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions. Windows Server Update Services By
using Windows Server Update Services (WSUS), administrators can deploy
the latest critical updates and security updates for Windows 2000
operating systems and later, Office XP and later, Exchange Server 2003,
and SQL Server 2000 to Windows 2000 and later operating systems. For
more information about how to deploy this security update using Windows
Server Update Services, visit the Windows Server Update Services Web site. Systems Management Server The following table provides the SMS detection and deployment summary for this security update. Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | Yes | Yes | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes | Yes |
For
SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update
Inventory Tool (SUIT), can be used by SMS to detect security updates.
See also Downloads for Systems Management Server 2.0. For
SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can
be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates.
SMS 2003 can also use the Microsoft Office Inventory Tool to detect
required updates for Microsoft Office applications. For more
information about the Office Inventory Tool and other scanning tools,
see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003. 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. 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 | Windows 2000 Service Pack 4:
Windows2000-kb943484-x86-enu /quiet | Installing without restarting | Windows 2000 Service Pack 4:
Windows2000- kb943484-x86-enu /norestart | Update log file | Windows 2000 Service Pack 4:
kb943484.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 | Windows 2000 Service Pack 4:
Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility located in the %Windir%\$NTUninstall kb943484$\Spuninst folder | File Information | See the next subsection, File Information, for the full file manifest | Registry Key Verification | For Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB943484\Filelist |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported editions of Windows 2000: ntdsa.dll | 5.0.2195.7147 | 16-Oct-2007 | 00:46 | 939,280 | sp3res.dll | 5.0.2195.7136 | 27-May-2007 | 18:26 | 6,258,688 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/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 | Display 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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. 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 | Display 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. | 5. | On the Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table.
Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
| |
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 not be included in a future service pack or update rollup as this is an optional component | Deployment | | Installing without user intervention | Windows XP Service Pack 2:
WindowsXP-KB931374-x86-ENU /quiet | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP- KB931374-x64-ENU.exe /quite | Installing without restarting | Windows XP Service Pack 2:
WindowsXP- KB931374-x86-ENU.exe /norestart | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP- KB931374-x64-ENU.exe /norestart | Update log file | Windows XP Service Pack 2: KB931374.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%\$NTUninstallKB931374$\Spuninst folder | File Information | See the next subsection, File Information, for the full file manifest | Registry Key Verification | For all supported 32-bit versions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB931374\Filelist | | For all supported x64 editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB931374\Filelist |
Note: Supported
editions of Windows XP Home Service Pack 2, Windows XP Tablet Edition
Service Pack 2, and Windows XP Media Center Edition Service Pack 2 are
not affected because they do not include ADAM or the Active Directory
server component. | |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported 32-bit editions of Windows XP: adamdsa.dll | 1.1.3790.4188 | 06-Jan-2008 | 17:35 | 1,631,744 | SP2GDR | adamdsa.dll | 1.1.3790.4188 | 06-Jan-2008 | 17:50 | 1,632,768 | SP2QFE |
For all supported 64-bit editions of Windows XP: adamdsa.dll | 1.1.3790.3043 | 10-Jan-2008 | 15:48 | 2,953,216 | X64 | SP1GDR | adamdsa.dll | 1.1.3790.3043 | 10-Jan-2008 | 15:48 | 2,956,288 | X64 | SP1QFE | adamdsa.dll | 1.1.3790.4188 | 10-Jan-2008 | 16:02 | 2,957,824 | X64 | SP2GDR | adamdsa.dll | 1.1.3790.4188 | 10-Jan-2008 | 15:46 | 2,959,360 | X64 | SP2QFE |
Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. This security update supports the following setup switches. |
/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 | Display 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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Removing the Update This security update supports the following setup switches. |
/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 | Display 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. | 5. | .On the Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table.
Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
| |
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 | For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb943484-x86-enu /quiet | | For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-kb943484-ia64-enu /quiet | | For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-kb943484-x64-enu /quiet | Installing without restarting | For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb943484-x86-enu /norestart | | For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-kb943484-ia64-enu /norestart | | For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-kb943484-x64-enu /norestart | Update log file | kb943484.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 | For all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003: Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility, located in the %Windir%\$NTUninstallKB943484$\Spuninst folder | File Information | See the next subsection, File Information, for the full file manifest | Registry Key Verification | For
all supported 32-bit editions, Itanium-based editions, and x64-based
editions of Windows Server 2003 Service Pack 1 and Windows Server 2003
Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\ kb943484\Filelist |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported 32-bit editions of Windows Server 2003: ntdsa.dll | 5.2.3790.3043 | 13-Nov-2007 | 21:33 | 1,515,520 | SP1GDR | ntdsa.dll | 5.2.3790.3043 | 13-Nov-2007 | 22:03 | 1,524,224 | SP1QFE | w03a2409.dll | 5.2.3790.3057 | 11-Dec-2007 | 21:40 | 28,672 | SP1QFE | ntdsa.dll | 5.2.3790.4188 | 13-Nov-2007 | 21:43 | 1,522,176 | SP2GDR | ntdsa.dll | 5.2.3790.4188 | 13-Nov-2007 | 21:36 | 1,525,248 | SP2QFE |
For all supported Itanium-based editions of Windows Server 2003: ntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:38 | 4,237,312 | IA-64 | SP1GDR | wntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:38 | 1,515,520 | X86 | SP1GDR\wow | ntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:38 | 4,257,280 | IA-64 | SP1QFE | w03a2409.dll | 5.2.3790.3057 | 19-Dec-2007 | 07:38 | 27,648 | IA-64 | SP1QFE | wntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:38 | 1,524,224 | X86 | SP1QFE\wow | ww03a2409.dll | 5.2.3790.3057 | 19-Dec-2007 | 07:38 | 28,672 | X86 | SP1QFE\wow | ntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:47 | 4,253,184 | IA-64 | SP2GDR | wntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:47 | 1,522,176 | X86 | SP2GDR\wow | ntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:35 | 4,260,352 | IA-64 | SP2QFE | wntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:35 | 1,525,248 | X86 | SP2QFE\wow |
For all supported x64-based editions of Windows Server 2003: ntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:34 | 2,947,072 | X64 | SP1GDR | wntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:34 | 1,515,520 | X86 | SP1GDR\wow | ntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:34 | 2,968,576 | X64 | SP1QFE | w03a2409.dll | 5.2.3790.3057 | 19-Dec-2007 | 07:34 | 29,184 | X64 | SP1QFE | wntdsa.dll | 5.2.3790.3043 | 19-Dec-2007 | 07:34 | 1,524,224 | X86 | SP1QFE\wow | ww03a2409.dll | 5.2.3790.3057 | 19-Dec-2007 | 07:34 | 28,672 | X86 | SP1QFE\wow | ntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:47 | 2,967,040 | X64 | SP2GDR | wntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:47 | 1,522,176 | X86 | SP2GDR\wow | ntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:35 | 2,970,112 | X64 | SP2QFE | wntdsa.dll | 5.2.3790.4188 | 19-Dec-2007 | 07:35 | 1,525,248 | X86 | SP2QFE\wow |
Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/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 | Display 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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Removing the Update This security update supports the following setup switches. |
/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 | Display 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. | 5. | On the Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table.
Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
| |
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 | For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb931374-x86-enu /quiet | | For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB931374-x64-enu /quiet | Installing without restarting | For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb931374-x86-enu /norestart | | For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB931374-x64-enu /norestart | Update log file | KB931374.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 | For all supported 32-bit editions and x64-based editions of Windows Server 2003: Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility, located in the %Windir%\$NTUninstallKB931374$\Spuninst folder | File Information | See the next subsection, File Information, for the full file manifest | Registry Key Verification | For
all supported 32-bit editions, x64-based editions of Windows Server
2003 Service Pack 1 and Windows Server 2003 Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB931374\Filelist |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported 32-bit editions of Windows Server 2003: adamdsa.dll | 1.1.3790.3043 | 13-Nov-2007 | 21:33 | 1,630,720 | SP1GDR | adamdsa.dll | 1.1.3790.3043 | 13-Nov-2007 | 22:03 | 1,631,232 | SP1QFE | adamdsa.dll | 1.1.3790.4188 | 13-Nov-2007 | 21:43 | 1,631,744 | SP2GDR | adamdsa.dll | 1.1.3790.4188 | 13-Nov-2007 | 21:36 | 1,632,768 | SP2QFE |
For all supported x64-based editions of Windows Server 2003: adamdsa.dll | 1.1.3790.3043 | 10-Jan-2008 | 15:48 | 2,953,216 | X64 | SP1GDR | adamdsa.dll | 1.1.3790.3043 | 10-Jan-2008 | 15:48 | 2,956,288 | X64 | SP1QFE | adamdsa.dll | 1.1.3790.4188 | 10-Jan-2008 | 16:02 | 2,957,824 | X64 | SP2GDR | adamdsa.dll | 1.1.3790.4188 | 10-Jan-2008 | 15:46 | 2,959,360 | X64 | SP2QFE |
Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/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 | Display 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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Removing the Update This security update supports the following setup switches. |
/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 | Display 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. | 5. | On the Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table.
Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. |
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
AcknowledgmentsMicrosoft thanks the following for working with us to help protect customers: | • | Thomas Garnier of SkyRecon for reporting the Active Directory Vulnerability – (CVE-2008-0088). |
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 (February 12, 2008): Bulletin published. |
| • | V1.1
(February 13, 2008): Bulletin updated to reflect the correct KB number
in the Registry Key Verification section for all supported x64-based
editions of Windows XP Professional with ADAM installed. |
| • | V1.2 (March 26, 2008): Bulletin updated to add KB link to the known issues section. |
|
