CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2025 · Wolfssl

CVE-2025-7394
Wolfssl vulnerability

In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RAND_bytes() after fork() and does not affect any internal TLS operations. Although RAND_bytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RAND_poll(), an additional code change was also made in wolfSSL to make RAND_bytes() behave similar to OpenSSL after a fork() call without calling RAND_poll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RAND_bytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Wolfssl. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Wolfssl runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Wolfssl products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.