CWE - CWE-336: Same Seed in Pseudo-Random Number Generator (PRNG) (4.19.1)
Home > CWE List > CWE-336: Same Seed in Pseudo-Random Number Generator (PRNG) (4.19.1)  
ID
  • Home
  • Who We Are User Stories History Documents Videos
  • Basics
    Root Cause Mapping   ►
    Guidance Quick Tips Examples
    How to Contribute Weakness Content FAQs Glossary
  • Top-N Lists   ►
    Top 25 Software Top Hardware Top 10 KEV Weaknesses
    CWE List   ►
    Current Version Reports Visualizations Releases Archive
    Downloads REST API
  • News   ►
    Current News Blog Podcast News Archive
    CWE Board Working Groups & Special Interest Groups Email Lists
  • Search CWE List Search Website

    CWE-336: Same Seed in Pseudo-Random Number Generator (PRNG)

    Weakness ID: 336
    Vulnerability Mapping: ALLOWED This CWE ID may be used to map to real-world vulnerabilities
    Abstraction: Variant Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.
    View customized information:
    For users who are interested in more notional aspects of a weakness. Example: educators, technical writers, and project/program managers. For users who are concerned with the practical application and details about the nature of a weakness and how to prevent it from happening. Example: tool developers, security researchers, pen-testers, incident response analysts. For users who are mapping an issue to CWE/CAPEC IDs, i.e., finding the most appropriate CWE for a specific issue (e.g., a CVE record). Example: tool developers, security researchers. For users who wish to see all available information for the CWE/CAPEC entry. For users who want to customize what details are displayed.
    ×

    Edit Custom Filter


    + Description
    A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized.
    + Extended Description
    Given the deterministic nature of PRNGs, using the same seed for each initialization will lead to the same output in the same order. If an attacker can guess (or knows) the seed, then the attacker may be able to determine the random numbers that will be produced from the PRNG.
    + Common Consequences
    Section HelpThis table specifies different individual consequences associated with the weakness. The Scope identifies the application security area that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in exploiting this weakness. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a weakness will be exploited to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.
    Impact Details

    Other; Bypass Protection Mechanism

    		Scope: Other, Access Control

    + Potential Mitigations
    Phase(s) Mitigation

    Architecture and Design
    Do not reuse PRNG seeds. Consider a PRNG that periodically re-seeds itself as needed from a high quality pseudo-random output, such as hardware devices.

    Architecture and Design; Requirements

    Strategy: Libraries or Frameworks

    Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems, or use the more recent FIPS 140-3 [REF-1192] if possible.
    + Relationships
    Section Help This table shows the weaknesses and high level categories that are related to this weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as PeerOf and CanAlsoBe are defined to show similar weaknesses that the user may want to explore.
    + Relevant to the view "Research Concepts" (View-1000)
    Nature Type ID Name
    ChildOf Base Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. 335 Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)
    + Relevant to the view "Architectural Concepts" (View-1008)
    Nature Type ID Name
    MemberOf Category Category - a CWE entry that contains a set of other entries that share a common characteristic. 1013 Encrypt Data
    + Modes Of Introduction
    Section HelpThe different Modes of Introduction provide information about how and when this weakness may be introduced. The Phase identifies a point in the life cycle at which introduction may occur, while the Note provides a typical scenario related to introduction during the given phase.
    Phase Note
    Implementation REALIZATION: This weakness is caused during implementation of an architectural security tactic.
    + Applicable Platforms
    Section HelpThis listing shows possible areas for which the given weakness could appear. These may be for specific named Languages, Operating Systems, Architectures, Paradigms, Technologies, or a class of such platforms. The platform is listed along with how frequently the given weakness appears for that instance.
    Languages

    Class: Not Language-Specific (Undetermined Prevalence)

    + Demonstrative Examples

    Example 1


    The following code uses a statistical PRNG to generate account IDs.

    (bad code)
    Example Language: Java 
    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.



    Example 2


    This code attempts to generate a unique random identifier for a user's session.

    (bad code)
    Example Language: PHP 
    function generateSessionID($userID){
    srand($userID);
    return rand();
    }

    Because the seed for the PRNG is always the user's ID, the session ID will always be the same. An attacker could thus predict any user's session ID and potentially hijack the session.

    If the user IDs are generated sequentially, or otherwise restricted to a narrow range of values, then this example also exhibits a Small Seed Space (CWE-339).



    + Selected Observed Examples

    Note: this is a curated list of examples for users to understand the variety of ways in which this weakness can be introduced. It is not a complete list of all CVEs that are related to this CWE entry.

    Reference Description
    SDK for JavaScript app builder for serverless code uses the same fixed seed for a PRNG, allowing cryptography bypass
    + Weakness Ordinalities
    Ordinality Description
    Primary
    (where the weakness exists independent of other weaknesses)
    + Detection Methods
    Method Details

    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 searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

    Effectiveness: High
    + Memberships
    Section HelpThis MemberOf Relationships table shows additional CWE Categories and Views that reference this weakness as a member. This information is often useful in understanding where a weakness fits within the context of external information sources.
    Nature Type ID Name
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 861 The CERT Oracle Secure Coding Standard for Java (2011) Chapter 18 - Miscellaneous (MSC)
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 905 SFP Primary Cluster: Predictability
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 1152 SEI CERT Oracle Secure Coding Standard for Java - Guidelines 49. Miscellaneous (MSC)
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 1346 OWASP Top Ten 2021 Category A02:2021 - Cryptographic Failures
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 1366 ICS Communications: Frail Security in Protocols
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 1414 Comprehensive Categorization: Randomness
    MemberOf CategoryCategory - a CWE entry that contains a set of other entries that share a common characteristic. 1439 OWASP Top Ten 2025 Category A04:2025 - Cryptographic Failures
    + Vulnerability Mapping Notes
    Usage ALLOWED
    (this CWE ID may be used to map to real-world vulnerabilities)
    Reason Acceptable-Use

    Rationale

    		This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.

    Comments

    		Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
    + Notes

    Maintenance

    As of CWE 4.5, terminology related to randomness, entropy, and predictability can vary widely. Within the developer and other communities, "randomness" is used heavily. However, within cryptography, "entropy" is distinct, typically implied as a measurement. There are no commonly-used definitions, even within standards documents and cryptography papers. Future versions of CWE will attempt to define these terms and, if necessary, distinguish between them in ways that are appropriate for different communities but do not reduce the usability of CWE for mapping, understanding, or other scenarios.
    + Taxonomy Mappings
    Mapped Taxonomy Name Node ID Fit Mapped Node Name
    PLOVER Same Seed in PRNG
    The CERT Oracle Secure Coding Standard for Java (2011) MSC02-J Generate strong random numbers
    + References
    [REF-267] Information Technology Laboratory, National Institute of Standards and Technology. "FIPS PUB 140-2: SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES". Annex C, Approved Random Number Generators. 2001-05-25.
    <https://csrc.nist.gov/files/pubs/fips/140-2/upd2/final/docs/fips1402.pdf>. (URL validated: 2025-05-21)
    [REF-1192] Information Technology Laboratory, National Institute of Standards and Technology. "FIPS PUB 140-3: SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES". 2019-03-22.
    <https://csrc.nist.gov/publications/detail/fips/140/3/final>.
    + Content History
    + Submissions
    Submission Date Submitter Organization
    2006-07-19
    (CWE Draft 3, 2006-07-19)     		PLOVER
    + Modifications
    Modification Date Modifier Organization
    2025-12-11
    (CWE 4.19, 2025-12-11)     		CWE Content Team MITRE
    updated Relationships, Weakness_Ordinalities
    2025-09-09
    (CWE 4.18, 2025-09-09)     		CWE Content Team MITRE
    updated References
    2023-10-26 CWE Content Team MITRE
    updated Demonstrative_Examples, Observed_Examples
    2023-06-29 CWE Content Team MITRE
    updated Mapping_Notes, Relationships
    2023-04-27 CWE Content Team MITRE
    updated Detection_Factors, Modes_of_Introduction, References, Relationships, Time_of_Introduction
    2021-10-28 CWE Content Team MITRE
    updated Relationships
    2021-07-20 CWE Content Team MITRE
    updated Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Potential_Mitigations, References
    2020-02-24 CWE Content Team MITRE
    updated Relationships
    2019-06-20 CWE Content Team MITRE
    updated Type
    2019-01-03 CWE Content Team MITRE
    updated Relationships, Taxonomy_Mappings
    2017-11-08 CWE Content Team MITRE
    updated Applicable_Platforms, Description, Modes_of_Introduction, Name, References, Relationships
    2014-07-30 CWE Content Team MITRE
    updated Demonstrative_Examples
    2012-05-11 CWE Content Team MITRE
    updated Relationships
    2011-09-13 CWE Content Team MITRE
    updated Potential_Mitigations, References
    2011-06-01 CWE Content Team MITRE
    updated Common_Consequences, Relationships, Taxonomy_Mappings
    2010-06-21 CWE Content Team MITRE
    updated Potential_Mitigations
    2009-12-28 CWE Content Team MITRE
    updated Potential_Mitigations
    2009-03-10 CWE Content Team MITRE
    updated Potential_Mitigations
    2008-09-08 CWE Content Team MITRE
    updated Relationships, Taxonomy_Mappings
    2008-07-01 Eric Dalci Cigital
    updated Time_of_Introduction
    2008-07-01 Sean Eidemiller Cigital
    added/updated demonstrative examples
    + Previous Entry Names
    Change Date Previous Entry Name
    2017-11-08 Same Seed in PRNG
    Page Last Updated: January 21, 2026