Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 24 Jan 2015 18:29:04 +0100
From: Gerhard Rieger <>
Subject: Socat security advisory 6 - Possible DoS with fork

Socat security advisory 6 - Possible DoS with fork

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

Vulnerability Id: (pending)

Severity: Low

  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
  sync-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.


Affected versions -
  2.0.0-b1 - 2.0.0-b7

Not affected or corrected versions and later
  2.0.0-b8 (to be released) and later


  The updated sources can be downloaded from:

   Credits to Peter Lobsinger

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.