CWE-332: Insufficient Entropy in PRNG

VariantDraftExploit Likelihood: Medium

The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-332 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-332, Insufficient Entropy in PRNG, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Libraries or Frameworks controls for Insufficient Entropy in PRNG

MITRE associates mitigation with Architecture and Design, Requirements, and Implementation; the listed strategies include Libraries or Frameworks; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-332 into implementation, review, and verification checks for the affected component.

CWE-332: Insufficient Entropy in PRNG — MITRE CWE

Triage CWE-332 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-332, Insufficient Entropy in PRNG, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-332

Apply MITRE's full root-cause mapping guidance when using CWE-332, Insufficient Entropy in PRNG. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-332 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-332, Insufficient Entropy in PRNG. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-332: Insufficient Entropy in PRNG?+

CWE-332: Insufficient Entropy in PRNG is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.

What are the security consequences of Insufficient Entropy in PRNG?+

If exploited, CWE-332 (Insufficient Entropy in PRNG) it can compromise Availability, Access Control and Other, leading to outcomes such as DoS: Crash, Exit, or Restart, Bypass Protection Mechanism and Other.

How do you prevent or mitigate Insufficient Entropy in PRNG?+

Recommended mitigations for CWE-332 include: Consider a PRNG that re-seeds itself as needed from high-quality pseudo-random output, such as hardware devices. When deciding which PRNG to use, look at its sources of entropy. Depending on what your security needs are, you may need to use a random number generator that always uses strong random data -- i.e., a random number generator that attempts to be strong but will fail in a weak way or will always provide some middle ground of protection through techniques like re-seeding. Generally, something that always provides a predictable amount of strength is preferable.

Which programming languages are affected by Insufficient Entropy in PRNG?+

CWE-332 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Insufficient Entropy in PRNG?+

MITRE documents real CVEs mapped to CWE-332, including [REF-1374] and CVE-2019-1715. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-332 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-332

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement