Red Hat Bugzilla – Bug 1367044
CVE-2015-1379: Possible DoS with fork
Last modified: 2017-08-01 14:57:03 EDT
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
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