Note: This is an archival copy of Security Sun Alert 201382 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1001055.1.
Sun Java System Directory Server 5.1 Service Pack 3
Sun Java System Directory Server 5.2
Sun Java System Directory Server Enterprise Edition
Date of Workaround Release
Date of Resolved Release
The Directory Server process "ns-slapd" may be terminated by a local or remote unprivileged user. This would cause a Denial of Service (DoS) to directory server services hosted on the affected system.
Sun acknowledges with thanks, iDefense (http://www.idefense.com), for bringing this issue to our attention.
This issue is also described in the following document:
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:
PatchZIP (Compressed Archive) versions:
If the described issue occurs, the Directory Server exits unexpectedly at the second request and a message similar to the following is logged for the first request:
[10/Oct/2006:10:32:10 +0200] conn=0 op=0 msgId=1 - ber decoding error (op=Compare; params=DN,Type,Value) [10/Oct/2006:10:32:10 +0200] conn=0 op=0 msgId=1 - RESULT err=2 tag=111 nentries=0 etime=0
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 Sun Java System Directory Server 5.2 Patch5. To upgrade to Directory Server 5.2patch5, apply the following patches:
For the Native Package Versions:
For the PatchZIP (Compressed Archive) versions:
This solution has no attachment