Base weakness
Draft
Log in
The product's random number generator produces a series of values which, when observed, can be used to infer a relatively small range of possibilities for the next value that could be generated.
Last updated
The output of a random number generator should not be predictable based on observations of previous values. In some cases, an attacker cannot predict the exact value that will be produced next, but can narrow down the possibilities significantly. This reduces the amount of effort to perform a brute force attack. For example, suppose the product generates random numbers between 1 and 100, but it always produces a larger value until it reaches 100. If the generator produces an 80, then the attacker knows that the next value will be somewhere between 81 and 100. Instead of 100 possibilities, the attacker only needs to consider 20.
3 recorded CVEs are caused by CWE-343 (Predictable Value Range from Previous Values). The highest-severity and most recent are shown first.
What can happen when CWE-343 is exploited.
Varies by Context
Affects: Other
Typically introduced during these phases of the software lifecycle.
Practical mitigations for CWE-343, grouped by where in the lifecycle they apply.
Increase the entropy used to seed a PRNG.
Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").
Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.
Common questions about CWE-343.
The product's random number generator produces a series of values which, when observed, can be used to infer a relatively small range of possibilities for the next value that could be generated.
3 recorded CVEs are attributed to CWE-343, including CVE-2017-6030, CVE-2017-7901, CVE-2014-5409.
Increase the entropy used to seed a PRNG.
Exploiting CWE-343 can lead to: Varies by Context.
3 recorded CVEs are caused by CWE-343; none are currently in CISA's KEV catalog of actively exploited flaws.
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Get alerted the moment a new CWE-343 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.