Per Allansson

The OpenSSL compatibility layer implementation had an issue with the `RAND poll()` function, potentially leading to predictable values returned from `RAND bytes()` after a `fork()` call. This could result in weak or predictable random numbers in applications using `RAND bytes()` and performing `fork()` operations. The issue does not affect internal TLS operations. A code change was implemented to reseed the Hash-DRBG after detecting a new process, similar to OpenSSL’s behavior.

A malicious TLS1.2 server can force a TLS1.3 client with downgrade capability to use a ciphersuite that it did not agree to and achieve a successful connection. This is because, aside from the extensions, the client was skipping fully parsing the server hello. The issue is related to the implementation of the TLS protocol in the WolfSSL library, which is associated with access control deficiencies.

The issue is related to the dtls1 listen function in OpenSSL, which does not properly isolate state information of independent data streams. This can be exploited by a remote attacker to cause a denial of service via crafted DTLS traffic. The attacker can generate DTLS traffic to cause the application to crash due to incorrect pointer dereferences.