CVE-2025-7394
In the OpenSSL compatibility layer implementation, the function RAND_p ...
Severity by source
Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by Julia (high).
Description
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.
Affected packages and fixed versions
| Source | Package | Fixed in |
|---|---|---|
| debian 11 | wolfssl | no fix listed |
| debian 12 | wolfssl | 5.5.4-2+deb12u2 |
| debian 13 | wolfssl | 5.7.2-0.1+deb13u1 |
| echo | wolfssl | 5.5.4-2+deb12u2 |
| julia::Julia Ecosystem Security Advisories | wolfSSL_jll | 5.8.4+0 |
| rapidfort alpine 3.20 | wolfssl | 5.9.1-r0 |
| rapidfort alpine 3.21 | wolfssl | 5.9.1-r0 |
| rapidfort alpine 3.22 | wolfssl | 5.9.1-r0 |
| rapidfort alpine 3.23 | wolfssl | 5.9.1-r0 |
| rapidfort alpine 3.24 | wolfssl | 5.9.1-r0 |
| rapidfort debian 12 | wolfssl | 0:5.7.2-0.1+deb13u1, 0:5.7.2-0.4 |
| rapidfort debian 13 | wolfssl | 0:5.7.2-0.1+deb13u1, 0:5.7.2-0.4 |