Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 790913

Summary:	NSS_Init* functions are not thread safe
Product:	Red Hat Enterprise Linux 6	Reporter:	RHEL Program Management <pm-rhel>
Component:	openldap	Assignee:	Jan Synacek <jsynacek>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.1	CC:	cww, goetz.reinicke, jonathan.underwood, jplans, jsynacek, jvcelak, magnus.moren, msvoboda, omoris, ovasik, pm-eus, rmeggins
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Mozilla NSS initialization functions are not implemented in a thread-safe way. Therefore, if multiple TLS operations were performed simultaneously on an LDAP server, a race condition between the TLS threads could occur. Consequently, the LDAP server terminated unexpectedly with a segmentation fault. With this update, a mutual exclusion (mutex) for Mozilla NSS initialization functions calls has been added to the code, which prevents this situation from occurring. The LDAP server no longer crashes when initializing a TLS connection.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-05 07:12:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	731168
Bug Blocks:	788730

Description RHEL Program Management 2012-02-15 17:30:01 UTC

This bug has been copied from bug #731168 and has been proposed
to be backported to 6.1 z-stream (EUS).

Comment 7 Miroslav Svoboda 2012-03-15 13:28:18 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Mozilla NSS initialization functions are not implemented in a thread-safe way. Therefore, if multiple TLS operations were performed simultaneously on an LDAP server, a race condition between the TLS threads could occur. Consequently, the LDAP server terminated unexpectedly with a segmentation fault. With this update, a mutual exclusion (mutex) for Mozilla NSS initialization functions calls has been added to the code, which prevents this situation from occurring. The LDAP server no longer crashes when initializing a TLS connection.

Comment 9 errata-xmlrpc 2012-04-05 07:12:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0453.html