CWE-342: Predictable Exact Value from Previous Values

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-342 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-342, Predictable Exact Value from Previous Values, 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 Predictable Exact Value from Previous Values

MITRE associates mitigation with Architecture and Design, Requirements, and Implementation; the listed strategies include Libraries or Frameworks; recorded impacts include Varies by Context. Use these source-defined anchors to turn CWE-342 into implementation, review, and verification checks for the affected component.

CWE-342: Predictable Exact Value from Previous Values — MITRE CWE

Triage CWE-342 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-342, Predictable Exact Value from Previous Values, 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-342

Apply MITRE's full root-cause mapping guidance when using CWE-342, Predictable Exact Value from Previous Values. 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-342 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-342, Predictable Exact Value from Previous Values. 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-342: Predictable Exact Value from Previous Values?+

CWE-342: Predictable Exact Value from Previous Values is a Common Weakness Enumeration (CWE) entry maintained by MITRE. An exact value or random number can be precisely predicted by observing previous values.

What are the security consequences of Predictable Exact Value from Previous Values?+

If exploited, CWE-342 (Predictable Exact Value from Previous Values) it can compromise Other, leading to outcomes such as Varies by Context.

How do you prevent or mitigate Predictable Exact Value from Previous Values?+

Recommended mitigations for CWE-342 include: Increase the entropy used to seed a PRNG.

Which programming languages are affected by Predictable Exact Value from Previous Values?+

CWE-342 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 Predictable Exact Value from Previous Values?+

MITRE documents real CVEs mapped to CWE-342, including CVE-2002-1463, CVE-1999-0074, CVE-1999-0077 and CVE-2000-0335. 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-342 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.

CWE-342: Predictable Exact Value from Previous Values

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

Observed CVE Examples (4)

CWE Relationships

Parent Weaknesses