Bug 1367044

Summary:	CVE-2015-1379: Possible DoS with fork
Product:	Red Hat Enterprise Linux 7	Reporter:	Gerd v. Egidy <gerd>
Component:	socat	Assignee:	Paul Wouters <pwouters>
Status:	CLOSED ERRATA	QA Contact:	Jan Blazek <jblazek>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	ksrot
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	1.7.3.2-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 18:57:03 UTC	Type:	Bug
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:
Bug Blocks:	1185711

Description Gerd v. Egidy 2016-08-15 11:31:37 UTC

Description of problem:
From Socat security advisory 6, CVE-2015-1379:

socats signal handler implementations are not async-signal-safe and can cause crash or freeze of socat processes

Details
  Socats signal handler implementations are not asnyc-signal-safe. When a signal
  is triggered while the process is within a non async-signal-safe function the
  signal handler will call a non async-signal-safe function too. POSIX specifies
  the behaviour in this situation as undefined. Dependend on involved functions,
  libraries, and operating system, the process can continue, freeze, or crash.
  Mostly this issue occurs when socat is in listening mode with fork option and
  a couple of child processes terminate at the same time.

http://www.dest-unreach.org/socat/contrib/socat-secadv6.txt

Please release an update with a fix for this issue.

Version-Release number of selected component (if applicable):
socat-1.7.2.2-5.el7

Comment 6 errata-xmlrpc 2017-08-01 18:57:03 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.

https://access.redhat.com/errata/RHBA-2017:2049