CWE-1279: Cryptographic Operations are run Before Supporting Units are Ready

Extended Description

Many cryptographic hardware units depend upon other hardware units to supply information to them to produce a securely encrypted result. For example, a cryptographic unit that depends on an external random-number-generator (RNG) unit for entropy must wait until the RNG unit is producing random numbers. If a cryptographic unit retrieves a private encryption key from a fuse unit, the fuse unit must be up and running before a key may be supplied.

Code Examples & CVEs

Demonstrative Examples

The following pseudocode illustrates the weak encryption resulting from the use of a pseudo-random-number generator output.

In the example above, first a check of RNG ready is performed. If the check fails, the RNG is ignored and a hard coded value is used instead. The hard coded value severely weakens the encrypted output.

BadPseudocode

If random_number_generator_self_test_passed() == TRUE 					  then Seed = get_random_number_from_RNG() 					  else Seed = hardcoded_number

The following pseudocode illustrates the weak encryption resulting from the use of a pseudo-random-number generator output.

GoodPseudocode

If random_number_generator_self_test_passed() == TRUE 					  then Seed = get_random_number_from_RNG() 					  else enter_error_state()

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1279 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1279, Cryptographic Operations are run Before Supporting Units are Ready, 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

Address Cryptographic Operations are run Before Supporting Units are Ready during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; recorded impacts include Varies by Context; the entry maps to CAPEC-97. Use these source-defined anchors to turn CWE-1279 into implementation, review, and verification checks for the affected component.

CWE-1279: Cryptographic Operations are run Before Supporting Units are Ready — MITRE CWE

Triage CWE-1279 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1279, Cryptographic Operations are run Before Supporting Units are Ready, 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-1279

Apply MITRE's full root-cause mapping guidance when using CWE-1279, Cryptographic Operations are run Before Supporting Units are Ready. 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-1279 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1279, Cryptographic Operations are run Before Supporting Units are Ready. 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-1279: Cryptographic Operations are run Before Supporting Units are Ready?+

CWE-1279: Cryptographic Operations are run Before Supporting Units are Ready is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Performing cryptographic operations without ensuring that the supporting inputs are ready to supply valid data may compromise the cryptographic result. Many cryptographic hardware units depend upon other hardware units to supply information to them to produce a securely encrypted result. For example, a cryptographic unit that depends on an external random-number-generator (RNG) unit for entropy must wait until the RNG unit is producing random numbers. If a cryptographic unit retrieves a private encryption key from a fuse unit, the fuse unit must be up and running before a key may be supplied.

What are the security consequences of Cryptographic Operations are run Before Supporting Units are Ready?+

If exploited, CWE-1279 (Cryptographic Operations are run Before Supporting Units are Ready) it can compromise Access Control, Confidentiality, Integrity, Availability, Accountability and Authentication, leading to outcomes such as Varies by Context.

How do you prevent or mitigate Cryptographic Operations are run Before Supporting Units are Ready?+

Recommended mitigations for CWE-1279 include: Best practices should be used to design cryptographic systems. Continuously ensuring that cryptographic inputs are supplying valid information is necessary to ensure that the encrypted output is secure.

Which programming languages are affected by Cryptographic Operations are run Before Supporting Units are Ready?+

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

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

A CWE (Common Weakness Enumeration) like CWE-1279 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-1279: Cryptographic Operations are run Before Supporting Units are Ready

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description