Note: This is an archival copy of Security Sun Alert 200086 as previously published on http://sunsolve.sun.com.
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000070.1.
Article ID : 1000070.1
Article Type : Sun Alerts (SURE)
Last reviewed : 2007-05-02
Audience : PUBLIC
Copyright Notice: Copyright © 2010, Oracle Corporation and/or its affiliates.

Directory Server May Hang Due to a Memory Leak in the Network Security Services (NSS) Software



Category
Security

Release Phase
Resolved

Product
Sun Java System Directory Server 5.2
Sun Java System Directory Server Enterprise Edition

Bug Id
6421471

Date of Workaround Release
27-APR-2007

Date of Resolved Release
03-MAY-2007

Impact

A local or remote unprivileged user may be able to cause the Sun Java System Directory Server 5.2 to become unresponsive or hang. This is a Denial of Service (DoS) due to a memory leak in the Network Security Services (NSS) software.

NSS is an open source project which adds support for SSL, S/MIME, and other Internet security standards to the Sun Java Enterprise System. Further information about NSS can be found at:

This issue is also described in CVE-2006-3127 at:


Contributing Factors

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):

PatchZIP (Compressed Archive) versions:

  • Sun Java System Directory Server 5.2
  • Sun Java System Directory Server 5.2 Patch2
  • Sun Java System Directory Server 5.2 Patch3
  • Sun Java System Directory Server 5.2 Patch4

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>

 


Symptoms

Should the described issue occur, the Directory Server will become unresponsive.


Workaround

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.


Resolution

This issue is addressed in Sun Java System Directory Server 5.2 Patch5. To upgrade to Directory Server 5.2patch5, apply the following patches:

PatchZIP (Compressed Archive) versions:

  • Solaris Sparc: 117665-04
  • Solaris x86: 117666-04
  • Linux: 117668-04
  • Windows: 117667-04
  • HP-UX: 117669-04
  • AIX: 117670-04


Modification History
Date: 02-MAY-2007
  • Updated Resolution section

Date: 03-MAY-2007
  • State: Resolved
  • Updated Resolution section


References

117668-04
117667-04
117669-04
117670-04
117665-04
117666-04




Attachments
This solution has no attachment