Base · Medium

CWE-335: Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)

The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.

CWE-335 · Base Level ·4 CVEs

Description

The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.

PRNGs are deterministic and, while their output appears random, they cannot actually create entropy. They rely on cryptographically secure and unique seeds for entropy so proper seeding is critical to the secure operation of the PRNG. Management of seeds could be broken down into two main areas: PRNGs require a seed as input to generate a stream of numbers that are functionally indistinguishable from random numbers. While the output is, in many cases, sufficient for cryptographic uses, the output of any PRNG is directly determined by the seed provided as input. If the seed can be ascertained by a third party, the entire output of the PRNG can be made known to them. As such, the seed should be kept secret and should ideally not be able to be guessed. For example, the current time may be a poor seed. Knowing the approximate time the PRNG was seeded greatly reduces the possible key space. Seeds do not necessarily need to be unique, but reusing seeds may open up attacks if the seed is discovered.

Potential Impact

Access Control, Other

Bypass Protection Mechanism, Other

Demonstrative Examples

The following code uses a statistical PRNG to generate account IDs.
Bad
private static final long SEED = 1234567890;public int generateAccountID() {Random random = new Random(SEED);return random.nextInt();}
Because the program uses the same seed value for every invocation of the PRNG, its values are predictable, making the system vulnerable to attack.
Both of these examples use a statistical PRNG seeded with the current value of the system clock to generate a random number:
Bad
Random random = new Random(System.currentTimeMillis());int accountID = random.nextInt();
Bad
srand(time());int randNum = rand();
An attacker can easily predict the seed used by these PRNGs, and so also predict the stream of random numbers generated. Note these examples also exhibit CWE-338 (Use of Cryptographically Weak PRNG).
This code grabs some random bytes and uses them for a seed in a PRNG, in order to generate a new cryptographic key.
Bad
# getting 2 bytes of randomness for the seeding the PRNG 
				  seed = os.urandom(2)
				  random.seed(a=seed)
				  key = random.getrandbits(128)
Since only 2 bytes are used as a seed, an attacker will only need to guess 2^16 (65,536) values before being able to replicate the state of the PRNG.

Detection Methods

  • Automated Static Analysis — Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then sea

Real-World CVE Examples

CVE IDDescription
CVE-2020-7010Cloud application on Kubernetes generates passwords using a weak random number generator based on deployment time.
CVE-2019-11495server uses erlang:now() to seed the PRNG, which results in a small search space for potential random seeds
CVE-2018-12520Product's PRNG is not seeded for the generation of session IDs
CVE-2016-10180Router's PIN generation is based on rand(time(0)) seeding.

Taxonomy Mappings

  • PLOVER: — PRNG Seed Error

Frequently Asked Questions

What is CWE-335?

CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.

How can CWE-335 be exploited?

Attackers can exploit CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)) to bypass protection mechanism, other. This weakness is typically introduced during the Implementation phase of software development.

How do I prevent CWE-335?

Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.

What is the severity of CWE-335?

CWE-335 is classified as a Base-level weakness (Medium abstraction). It has been observed in 4 real-world CVEs.