Bug 98593

Summary: CAN-2002-1563 Stunnel unsafe SIGCHLD handler
Product: Red Hat Enterprise Linux 2.1 Reporter: Mark J. Cox <mjc>
Component: stunnelAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1Keywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://marc.theaimsgroup.com/?l=stunnel-users&m=103600188215117
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-07-25 13:17:04 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:

Description Mark J. Cox 2003-07-04 10:24:21 UTC 
When configured to listen for incoming connections (instead of being
invoked by xinetd), stunnel can either be configured to start either a
thread or a process to handle each new connection. If Stunnel is configured
to start a new child process to handle each connection, it will receive a
SIGCHLD signal when that child exits. 

Stunnel versions prior to 4.04 would perform tasks in the SIGCHLD signal
handler which, if interrupted by another SIGCHLD signal, could be unsafe.
This could lead to a Denial of Service.

Errata with backported security fix in progress
Comment 1 Mark J. Cox 2003-07-25 13:17:04 UTC 
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2003-223.html