Applications that use Lightweight Directory Access Protocol (LDAP) over Secure Sockets Layer (SSL) do not perform revocation checking of the server certificate in Windows Server 2003 with Service Pack 1 (911647)



The information in this article applies to:

  • Microsoft Windows Server 2003 SP1, when used with:
    • Microsoft Windows Server 2003, Standard Edition
    • Microsoft Windows Server 2003, Enterprise Edition
    • Microsoft Windows Server 2003, Standard x64 Edition
    • Microsoft Windows Server 2003, Enterprise x64 Edition
    • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

SYMPTOMS

You have certain applications that use the Windows Lightweight Directory Access Protocol (LDAP) APIs to access an LDAP directory over Secure Sockets Layer (SSL) on a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer. However, these applications do not perform revocation checking of the certificate that is issued to the LDAP server.

CAUSE

This problem occurs because of the following reasons.

In a Windows operating system, Microsoft Security Channel (SChannel) implements SSL and Transport Layer Security (TLS). By default, SChannel does not perform revocation checking of server authentication certificates. However, developers can modify this behavior by setting the appropriate SChannel flags before it calls into the component.

Additionally, the Wldap32.dll file implements the LDAP API in Windows. Developers can use the Wldap32.dll file calls to connect to a directory server over SSL or over TLS. The Wldap32.dll file depends on SChannel to help provide security for these connections. When the Wldap32.dll file calls into SChannel, the Wldap32.dll file does not modify the default behavior of SChannel authentication.

Therefore, when you use the Wldap32.dll file to connect to a directory server over SSL or TLS, the client computer does not perform revocation checking of the server authentication certificate.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Windows Server 2003 SP1 installed to apply this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later 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 item in Control Panel.Windows Server 2003 with SP1, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Wldap32.dll5.2.3790.2594178,68815-Dec-200505:27x86
Windows Server 2003 with SP1, x64-based versions
File nameFile versionFile sizeDateTimePlatformService pack requirementService branch
Wldap32.dll5.2.3790.2594399,87214-Dec-200513:56x64SP1Not Applicable
Wwldap32.dll5.2.3790.2594178,68814-Dec-200513:56x86SP1WOW
Windows Server 2003 with SP1, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformService pack requirementService branch
Wldap32.dll5.2.3790.2594454,14414-Dec-200513:57IA-64SP1Not Applicable
Wwldap32.dll5.2.3790.2594178,68814-Dec-200513:57x86SP1WOW

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply this hotfix, a code change occurs in the Wldap32.dll file. This code change lets developers modify how the Wldap32.dll file uses SChannel. Additionally, there is a new LDAP session option that lets developers set the SChannel flags.

The new LDAP session option is as follows:
define LDAP_OPT_SCH_FLAGS  0x43
For more information about how to set LDAP session options, visit the following Microsoft Developer Network (MSDN) Web site:If the LDAP_OPT_SCH_FLAGS option is not set, the default SChannel flags that are used by the Wldap32.dll file are as follows:
(SCH_CRED_USE_DEFAULT_CREDS | SCH_CRED_AUTO_CRED_VALIDATION)
For more information about SChannel flags, visit the following Microsoft MSDN Web site:Note This change in behavior does not affect applications that are already compiled and installed. This article describes functionality that can now be applied in Windows Server 2003 Service Pack 2 (SP2). For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MinorLast Reviewed:10/3/2006
Keywords:kbBug kbfix kbQFE kbhotfixserver kbpubtypekc KB911647 kbAudITPRO