Security Bulletin
Microsoft Security Bulletin MS07-039 - Critical
Vulnerability in Windows Active Directory Could Allow Remote Code Execution (926122)
Published: July 10, 2007 | Updated: July 12, 2007
Version: 1.1
General Information
Executive Summary
This critical security update resolves a privately reported vulnerability in implementations of Active Directory on Windows 2000 Server and Windows Server 2003 that could allow remote code execution or a denial of service condition. Attacks attempting to exploit this vulnerability would most likely result in a denial of service condition. However remote code execution could be possible. On Windows Server 2003 an attacker must have valid logon credentials to exploit this vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.
This is a critical security update for supported editions of Windows 2000 and an important security update for supported editions of 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 the number of convertible attributes in the client LDAP request. For more information about the vulnerability, see the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately.
Known Issues. None.
Affected and Non-Affected Software
The following software have been tested to determine which editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| Operating System | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by This Update |
|---|---|---|---|
| Microsoft Windows 2000 Server Service Pack 4 | Remote Code Execution | Critical | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Remote Code Execution | Important | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Remote Code Execution | Important | None |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Remote Code Execution | Important | None |
Non-Affected Software
| Operating System |
|---|
| Windows 2000 Professional Service Pack 4 |
| Windows XP Service Pack 2 |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 |
| Windows Vista |
| Windows Vista x64 Edition |
| Active Directory Application Mode (ADAM) Service Pack 1 |
Note: These editions of Windows are not affected because they do not include the Active Directory server component.
Frequently Asked Questions (FAQ) Related to This Security Update
I do not have any of the Affected Software installed. Why am I being offered the security update?
While the vulnerabilities addressed by this security update only affect Windows 2000 Server and Windows Server 2003 systems that are functioning in a domain controller role, the vulnerable code exists on all supported editions of Windows 2000 and Windows 2003. This update is offered to all systems that contain the vulnerable code.
I have ADAM installed, what should I do?
The vulnerable code does not exist in ADAM Service Pack 1. However, vulnerable code does exist in versions previous to ADAM Service Pack 1. We recommend installing Service Pack 1 for ADAM. For more information on ADAM Service Pack 1, please visit the ADAM SP1 download site.
What is ADAM?
ADAM provides data storage and retrieval for directory-enabled applications, without the dependencies that are required for the Active Directory service. ADAM provides much of the same functionality as Active Directory, but it does not require the deployment of domains or domain controllers, and the directory schema for ADAM is completely independent of the enterprise schema you may be using in an Active Directory domain. You can run multiple instances of ADAM concurrently on a single computer, with an independently managed schema for each ADAM instance.
For more information on ADAM, please see the Introduction to Active Directory Application Mode.
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 the following Microsoft Support Lifecycle. For more information about the extended security update support period for these software releases, visit the Microsoft Product Support Services Web site.
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 the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Active Directory Remote Code Execution Vulnerability - CVE-2007-0040 | Active Directory Denial of Service Vulnerability - CVE- 2007-3028 | Aggregate Severity Rating |
|---|---|---|---|
| Windows 2000 Server Service Pack 4 | Critical \ Remote Code Execution | Important \ Denial Of Service | Critical |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important \ Remote Code Execution | None | Important |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important \ Remote Code Execution | None | Important |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Important \ Remote Code Execution | None | Important |
Windows Active Directory Remote Code Execution Vulnerability- CVE-2007-0040
A remote code execution vulnerability exists in the way that Active Directory validates a LDAP request. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0040.
Mitigating Factors for Windows Active Directory Remote Code Execution Vulnerability- CVE-2007-0040
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:
- For customers who require the affected component, firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
- Attacks attempting to exploit this vulnerability would most likely result in a denial of service condition. However remote code execution could be possible.
- On Windows Server 2003 an attacker must have valid logon credentials to exploit this vulnerability; the vulnerability can not be exploited by an anonymous user.
Workarounds for Windows Active Directory Remote Code Execution Vulnerability- CVE-2007-0040
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 the following at the firewall:
TCP port 389This port is used to initiate 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, visit TCP and UDP Port Assignments.
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.
FAQ for Windows Active Directory Remote Code Execution Vulnerability- CVE-2007-0040
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
Note. Attacks attempting to exploit this vulnerability would most likely result in a denial of service condition. However remote code execution could be possible and the scope is therefore larger than only a denial of service.
What causes the vulnerability?
The LDAP service performs insufficient checks for the number of convertible attributes included in a LDAP request.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
How could an attacker exploit the vulnerability?
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, the attacker must have valid authentication credentials to try to exploit this vulnerability.
What systems are primarily at risk from the vulnerability?
LDAP is a requirement for Active Directory. Therefore, any Windows 2000 Server or Windows Server 2003 that is running as an Active Directory Server is affected by this vulnerability.
Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet. However common firewall practices contain Active Directory requests to within the enterprise infrastructure. Firewall best practices can help protect against attacks that originate from the Internet.
What is LDAP?
LDAP (Lightweight Directory Access Protocol) is an industry-standard protocol that enables authorized users to query or modify the data in a meta directory. In Windows Server 2000 and Windows Server 2003, LDAP is one protocol used to access data in the Active Directory.
What does the update do?
The update removes the vulnerability by performing checks for the number of convertible attributes included in an LDAP request.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
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.
Windows Active Directory Denial of Service Vulnerability- CVE-2007-3028
A denial of service vulnerability exists in the way that Microsoft Active Directory validates a client-sent LDAP request. An attacker could exploit the vulnerability by sending a specially crafted LDAP request to a server running Active Directory. An attacker who successfully exploited this vulnerability could cause the server to temporarily stop responding.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-3028.
Mitigating Factors for Windows Active Directory Denial of Service Vulnerability- CVE-2007-3028
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:
- For customers who require the affected component, firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
- Windows Server 2003 editions are not affected by this vulnerability.
Workarounds for Windows Active Directory Denial of Service Vulnerability- CVE-2007-3028
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 the following at the firewall:
TCP ports 389 and 3268These ports are used to initiate connections with the affected component. Blocking these 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, visit TCP and UDP Port Assignments.
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.
FAQ for Windows Active Directory Denial of Service Vulnerability- CVE-2007-3028
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 temporarily stop responding. During that time, the server would be unable to respond to requests. 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 incorrect decoding of data that is sent in the client LDAP request.
How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by sending a specially crafted request to an affected system. The message could then cause the affected system to stop responding.
What systems are primarily at risk from the vulnerability?
LDAP is a requirement for Active Directory. Therefore, any Windows 2000 Server that is running as an Active Directory Server is affected by this vulnerability.
Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet. However common firewall practices contain Active Directory requests to within the enterprise infrastructure. Firewall best practices can help protect against attacks that originate from the Internet.
What is LDAP?
LDAP (Lightweight Directory Access Protocol) is an industry-standard protocol that enables authorized users to query or modify the data in a meta directory. In Windows Server 2000 and Windows Server 2003, LDAP is one protocol used to access data in the Active Directory.
What does the update do?
The update removes the vulnerability by validating the client sent LDAP request logic.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
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.
Update Information
Detection and Deployment Tools and Guidance
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 at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
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), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). 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 Web site. The following table provides the MBSA detection summary for this security update.
| Software | MBSA 1.2.1 | MBSA 2.0.1 |
|---|---|---|
| Microsoft Windows 2000 Server Service Pack 4 | Yes | Yes |
| Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2 | Yes | Yes |
| Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2 | No | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Microsoft Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes |
For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
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.
| Software | SMS 2.0 | SMS 2003 |
|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
| Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2 | Yes | Yes |
| Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2 | No | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes |
SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.
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. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For more information about SMS, visit the SMS Web site.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 2000 Server (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | Windows 2000 Server Service Pack 4:\ Windows2000-kb926122-x86-enu /quiet |
| Installing without restarting | Windows 2000 Server Service Pack 4:\ Windows2000-kb926122-Windows2000sp4-x86-enu /norestart |
| Update log file | Windows 2000 Server Service Pack 4:\ KB926122.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | 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%$NTUninstallKB926122$\Spuninst folder |
| File Information | See the subsection, File Information, in this section for the full file manifest |
| Registry Key Verification | For Windows 2000 Server Service Pack 4:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB926122\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported editions of Windows 2000 Server:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| ntdsa.dll | 5.0.2195.7135 | 22-Apr-2007 | 17:52 | 939,280 |
| sp3res.dll | 5.0.2195.7135 | 18-Apr-2007 | 16:36 | 6,239,232 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
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.
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.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | All supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:\ Windowsserver2003-kb926122-x86-enu /quiet |
| Installing without restarting | All supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:\ Windowsserver2003-kb926122-x86-enu /norestart |
| Update log file | KB926122.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | 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 | All supported 32-bit editions, x64 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 Use the Spuninst.exe utility, located in the %Windir%$NTUninstallKB926122$\Spuninst folder |
| File Information | See the subsection, File Information, in this section for the full file manifest |
| Registry Key Verification | All supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB926122\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| ntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 17:49 | 1,515,520 | SP1GDR |
| ntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 17:59 | 1,521,664 | SP1QFE |
| w03a2409.dll | 5.2.3790.2926 | 26-Apr-2007 | 22:22 | 27,648 | SP1QFE |
| ntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:04 | 1,522,176 | SP2GDR |
| ntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 17:53 | 1,522,176 | SP2QFE |
| w03a2409.dll | 5.2.3790.4070 | 27-Apr-2007 | 04:04 | 453,632 | SP2QFE |
For all supported x64 editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| ntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 19:02 | 2,946,560 | X64 | SP1GDR |
| Wntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 19:02 | 1,515,520 | X86 | SP1GDR\wow |
| ntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 19:02 | 2,964,992 | X64 | SP1QFE |
| w03a2409.dll | 5.2.3790.2926 | 29-Apr-2007 | 19:02 | 28,160 | X64 | SP1QFE |
| Wntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 19:02 | 1,521,664 | X86 | SP1QFE\wow |
| ww03a2409.dll | 5.2.3790.2926 | 29-Apr-2007 | 19:02 | 27,648 | X86 | SP1QFE\wow |
| ntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 19:04 | 2,966,528 | X64 | SP2GDR |
| Wntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 19:04 | 1,522,176 | X86 | SP2GDR\wow |
| ntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 2,966,528 | X64 | SP2QFE |
| w03a2409.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 454,144 | X64 | SP2QFE |
| Wntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 1,522,176 | X86 | SP2QFE\wow |
| ww03a2409.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 453,632 | X86 | SP2QFE\wow |
For all supported Itanium-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| ntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 18:58 | 4,237,312 | IA-64 | SP1GDR |
| Wntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 18:58 | 1,515,520 | X86 | SP1GDR\wow |
| ntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 18:59 | 4,250,624 | IA-64 | SP1QFE |
| w03a2409.dll | 5.2.3790.2926 | 29-Apr-2007 | 18:59 | 26,624 | IA-64 | SP1QFE |
| Wntdsa.dll | 5.2.3790.2926 | 29-Apr-2007 | 18:59 | 1,521,664 | X86 | SP1QFE\wow |
| ww03a2409.dll | 5.2.3790.2926 | 29-Apr-2007 | 18:59 | 27,648 | X86 | SP1QFE\wow |
| ntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 19:03 | 4,253,696 | IA-64 | SP2GDR |
| Wntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 19:03 | 1,522,176 | X86 | SP2GDR\wow |
| ntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 4,253,696 | IA-64 | SP2QFE |
| w03a2409.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 452,608 | IA-64 | SP2QFE |
| Wntdsa.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 1,522,176 | X86 | SP2QFE\wow |
| ww03a2409.dll | 5.2.3790.4070 | 29-Apr-2007 | 18:59 | 453,632 | X86 | SP2QFE\wow |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program |
| /ER | Enables extended error reporting |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
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.
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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Peter Winter-Smith of NGSSoftware, for reporting the Windows Active Directory Denial of Service Vulnerability-CVE-2007-3028.
- Neel Mehta of IBM Internet Security Systems x-Force, for reporting the Windows Active Directory Remote Code Execution Vulnerability-CVE-2007-0040.
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
V1.0 (July 10, 2007): Bulletin published.
V1.1 (July 12, 2007): Bulletin Revised: Updating bulletin to add FAQ section for ADAM dependencies and deployment to all 2000 and 2003 systems.
Built at 2014-04-18T13:49:36Z-07:00