Description
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.
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.
Potential Impact
Other
Varies by Context
Mitigations & Prevention
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.
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Predictable Value Range from Previous Values
Frequently Asked Questions
What is CWE-343?
CWE-343 (Predictable Value Range from Previous Values) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. 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.
How can CWE-343 be exploited?
Attackers can exploit CWE-343 (Predictable Value Range from Previous Values) to varies by context. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-343?
Key mitigations include: Increase the entropy used to seed a PRNG.
What is the severity of CWE-343?
CWE-343 is classified as a Base-level weakness (Medium abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.