CVE-2025-7394: Infoleak
In the OpenSSL compatibility layer implementation, the function RANDpoll() was not behaving as expected and leading to the potential for predictable values returned from RANDbytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RANDbytes() and doing fork() operations. This only affects applications explicitly calling RANDbytes() after fork() and does not affect any internal TLS operations. Although RANDbytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RANDpoll(), an additional code change was also made in wolfSSL to make RANDbytes() behave similar to OpenSSL after a fork() call without calling RANDpoll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RANDbytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-7394?
CVE-2025-7394 is categorized as a medium severity vulnerability due to the potential for predictable random number generation.
How do I fix CVE-2025-7394?
To fix CVE-2025-7394, upgrade to a patched version of OpenSSL or wolfSSL where the RAND_poll() function behavior has been corrected.
What impact does CVE-2025-7394 have on applications?
CVE-2025-7394 may lead to applications that rely on RAND_bytes() producing weak or predictable random numbers, compromising security.
Which software is affected by CVE-2025-7394?
CVE-2025-7394 affects OpenSSL and wolfSSL libraries, specifically in versions prior to the fix for this vulnerability.
Is CVE-2025-7394 exploitable?
CVE-2025-7394 is potentially exploitable in applications that utilize random number generation after a fork, increasing the risk of security vulnerabilities.