Note: This is an archival copy of Security Sun Alert 200717 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000568.1.
Sun Java System Directory Server 5.2
Date of Workaround Release
Date of Resolved Release
A local or remote unprivileged user may be able to prevent an LDAP server from responding to LDAP client requests. This is a Denial of Service (DoS) as LDAP clients referencing the LDAP server may experience hangs or slow performance. Users may no longer be able to login on affected LDAP client systems.
This issue is also described in CVE-2006-0647 at http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0647
This issue can occur in the following releases for all platforms (Solaris 8, 9, and 10 on Solaris SPARC and Solaris x86 Platforms, Linux, Windows, HP-UX, and AIX):
Native Package Versions:
without patch 122476-01
PatchZIP (Compressed Archive) versions:
without patch 122476-01
Note: Sun ONE Directory Server 5.1 and earlier versions are not affected by this issue.
To determine the version of Directory Server running on a system, the following command can be used:
$ cd <installation directory>/bin/slapd/server[/64] $ ./ns-slapd -V -D <instance-directory>
Should the described issue occur, the LDAP server will no longer respond to client LDAP requests. The LDAP server process, ns-slapd, may not be running on the LDAP server. If the LDAP server process is no longer running, there may a message similar to the following about failing to calloc a random number of bytes in the error log:
ERROR<5135> - Resource Limit - conn=-1 op=-1 msgId=-1 - Memory allocation error calloc of 8248 bytes failed; errno 11
There is no Workaround for this issue. To recover from an unresponsive LDAP server instance, the following command can be used to restart the LDAP server process:
On UNIX systems (usually as root user):
# <server instance path>/start-slapd
On Windows systems, open the "Services" panel and start the service manually.
This issue is addressed in the following releases for all platforms (Solaris 8, 9, and 10 on Solaris SPARC and Solaris x86 Platforms, Linux, Windows, HP-UX, and AIX):
Note: Versions previous to Sun Java System Directory Server 5 2005Q4 or Sun Java System Directory Server 5.2 Patch4 must be upgraded to these versions before applying the patch.
This issue can also be addressed by upgrading to Directory Server 5.2patch5 by applying the following patches:
For the Native Package Versions:
For the PatchZIP (Compressed Archive) versions:
This solution has no attachment