CWE · MITRE source
CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
When a non-cryptographic PRNG is used in a cryptographic context, it can expose the cryptography to certain types of attacks. Often a pseudo-random number generator (PRNG) is not designed for cryptography. Sometimes a mediocre source of randomness is sufficient or preferable for algorithms that use random numbers. Weak generators generally take less processing power and/or do not use the precious, finite, entropy sources on a system. While such PRNGs might have very useful features, these same features could be used to break the cryptography.
Last updated: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AT-5 | Contacts with Security Groups and Associations | AT | Security associations share details on cryptographically weak PRNGs, helping avoid their implementation in security-critical functions. |
SC-12 | Cryptographic Key Establishment and Management | SC | Cryptographic key management standards require cryptographically strong PRNGs for key material, blocking use of weak generators. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-29868 | 6.5 | 9.1 | 0.7844 | 2024-06-24 |
CVE-2009-2367 | 3.9 | 9.8 | 0.3233 | 2009-07-08 |
CVE-2024-31497 | 2.5 | 5.9 | 0.2197 | 2024-04-15 |
CVE-2019-16303 | 2.1 | 9.8 | 0.0190 | 2019-09-14 |
CVE-2017-18021 | 2.0 | 9.8 | 0.0058 | 2018-01-05 |
CVE-2015-9435 | 2.0 | 9.8 | 0.0052 | 2019-09-26 |
CVE-2020-28642 | 2.0 | 9.8 | 0.0070 | 2020-11-16 |
CVE-2019-14480 | 2.0 | 9.8 | 0.0029 | 2020-12-16 |
CVE-2021-3538 | 2.0 | 9.8 | 0.0093 | 2021-06-02 |
CVE-2011-4574 | 2.0 | 9.8 | 0.0043 | 2021-10-27 |
CVE-2021-43799 | 2.0 | 8.6 | 0.0527 | 2022-01-25 |
CVE-2022-44796 | 2.0 | 9.8 | 0.0050 | 2022-11-07 |
CVE-2023-2884 | 2.0 | 9.8 | 0.0013 | 2023-05-25 |
CVE-2023-36993 | 2.0 | 9.8 | 0.0013 | 2023-07-07 |
CVE-2024-40762 | 2.0 | 9.8 | 0.0004 | 2025-01-09 |
CVE-2025-3495 | 2.0 | 9.8 | 0.0049 | 2025-04-16 |
CVE-2025-7394 | 2.0 | 9.8 | 0.0008 | 2025-07-18 |
CVE-2025-59390 | 2.0 | 9.8 | 0.0005 | 2025-11-26 |
CVE-2025-66565 | 2.0 | 9.8 | 0.0007 | 2025-12-09 |
CVE-2025-68932 | 2.0 | 9.8 | 0.0004 | 2025-12-27 |
CVE-2025-15578 | 2.0 | 9.8 | 0.0006 | 2026-02-16 |
CVE-2026-2439 | 2.0 | 9.8 | 0.0007 | 2026-02-16 |
CVE-2025-40926 | 2.0 | 9.8 | 0.0007 | 2026-03-05 |
CVE-2025-15604 | 2.0 | 9.8 | 0.0002 | 2026-03-28 |
CVE-2026-3256 | 2.0 | 9.8 | 0.0002 | 2026-03-28 |