CVE-2025-7394CWE-200

In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values…

High · published July 18, 2025

CVSS v4.0
7.0
EPSS
0%
Percentile
38.8
In the wild
Unconfirmed
What it is

⚡ A sneaky issue in the OpenSSL compatibility layer can lead to predictable random numbers after a fork! Imagine generating a lottery ticket with a number everyone can guess! 🎟️ Think of it like a bakery where the recipe for bread is used before and after a delivery. If the baker doesn’t check the ingredients after the delivery, the new batch might have stale or predictable flavors, just like the random numbers generated by RAND_bytes() after fork() without calling RAND_poll(). This vulnerability can lead to critical security issues, allowing attackers to predict random values and potentially compromise sensitive data or cryptographic operations. If an application relies on these weak random numbers, it could be exposed to all sorts of cyber mischief, from unauthorized access to data breaches!

Put simply

Think of it like a bakery where the recipe for bread is used before and after a delivery. If the baker doesn’t check the ingredients after the delivery, the new batch might have stale or predictable flavors, just like the random numbers generated by RAND_bytes() after fork() without calling RAND_poll(). The issue lies in the RAND_poll() function not behaving as intended, resulting in predictable values from RAND_bytes() when called post-fork. If applications use RAND_bytes() without the recommended call to RAND_poll() after a fork, they may generate weak random numbers, putting security at risk.

What to do

This vulnerability can lead to critical security issues, allowing attackers to predict random values and potentially compromise sensitive data or cryptographic operations. If an application relies on these weak random numbers, it could be exposed to all sorts of cyber mischief, from unauthorized access to data breaches! To protect yourself, update to the latest version of wolfSSL, where RAND_bytes() now properly reseeds after a fork operation. Audit your applications to ensure they call RAND_poll() after forking, and review your use of RAND_bytes() to mitigate any risks. Don't wait—get on top of this! You've got this! By taking these steps, your application will be fortified against potential vulnerabilities. 🛡️

The record
Technical detail
CVSS v4.0
7.0 · HIGH
Vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
EPSS
0.00459 · 38.8th percentile
Weakness
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
Published
2025-07-18T22:34Z
EPSS history
Timeline
  • 18 JUL 22:34Z
    In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values…
    cvelistv5