CVE-2014-0016

stunnel anterior a 5.00, cuando utilizando hilo de bifurcación, no actualiza debidamente el estado del generador de números psuedoaleatorios OpenSSL (PRNG), lo que causa que hijos posteriores con el mismo proceso ID utilicen el mismo pool de entropía y permite a atacantes remotos obtener claves privadas para certificados EC (ECDSA) o DSA.

A flaw was found in the way stunnel, a socket wrapper which can provide SSL support to ordinary applications, performed initialization of PRNG after fork. When accepting a new connection, the server forks and the child process handles the request. The RAND_bytes() function of openssl doesn't reset its state after the fork, but seeds the PRNG with the output of time. The most important consequence is that servers using EC or DSA certificates may under certain conditions leak their private key. The updated packages fix this issue by using threads instead of new processes to handle connections. Also an issue has been corrected where the directory for the pid file was not being created when the package is installed. An issue currently exists in Mageia 4 where it fails trying to use FIPS SSL. This can be worked around by adding fips = no into the config.