Vulnerabilities > Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-12-01 | CVE-2021-3990 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Showdoc showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) | 4.3 |
| 2021-10-27 | CVE-2011-4574 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Polarssl PolarSSL versions prior to v1.1 use the HAVEGE random number generation algorithm. | 7.5 |
| 2021-09-23 | CVE-2021-22948 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Revive-Adserver Revive Adserver Vulnerability in the generation of session IDs in revive-adserver < 5.3.0, based on the cryptographically insecure uniqid() PHP function. | 7.1 |
| 2021-08-30 | CVE-2021-27913 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Acquia Mautic The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control This issue affects: Mautic Mautic versions prior to 3.3.4; versions prior to 4.0.0. | 3.5 |
| 2021-08-06 | CVE-2021-37553 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2021.2.16363, an insecure PRNG was used. | 5.0 |
| 2021-08-04 | CVE-2021-3678 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Showdoc showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) | 4.3 |
| 2021-06-09 | CVE-2021-0131 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Intel Secl-Dc Use of cryptographically weak pseudo-random number generator (PRNG) in an API for the Intel(R) Security Library before version 3.3 may allow an authenticated user to potentially enable information disclosure via network access. | 4.0 |
| 2021-06-02 | CVE-2021-3538 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Go.Uuid Project Go.Uuid A flaw was found in github.com/satori/go.uuid in versions from commit 0ef6afb2f6cdd6cdaeee3885a95099c63f18fc8c to d91630c8510268e75203009fe7daf2b8e1d60c45. | 7.5 |
| 2021-05-21 | CVE-2008-3280 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Openid It was found that various OpenID Providers (OPs) had TLS Server Certificates that used weak keys, as a result of the Debian Predictable Random Number Generator (CVE-2008-0166). | 4.3 |
| 2021-05-05 | CVE-2021-29245 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Btcpayserver Btcpay Server BTCPay Server through 1.0.7.0 uses a weak method Next to produce pseudo-random values to generate a legacy API key. | 5.0 |