|
|
|
|
| |
Credit:
The information has been provided by Microsoft Product Security.
The original article can be found at: http://www.microsoft.com/technet/security/bulletin/ms08-003.mspx
|
| |
Affected Software
Software Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by This Update
* 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
Active Directory Vulnerability - CVE-2008-0088
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.
CVE Information:
CVE-2008-0088
Workarounds for Active Directory Vulnerability - CVE-2008-0088
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.
FAQ for Active Directory Vulnerability - CVE-2008-0088
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.
|
|
|
|
|
