CWE-1304: Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation

BaseDraft

The product performs a power save/restore operation, but it does not ensure that the integrity of the configuration state is maintained and/or verified between the beginning and ending of the operation.

View on MITRE
Back to CWE Lookup

Extended Description

Before powering down, the Intellectual Property (IP) saves current state (S) to persistent storage such as flash or always-on memory in order to optimize the restore operation. During this process, an attacker with access to the persistent storage may alter (S) to a configuration that could potentially modify privileges, disable protections, and/or cause damage to the hardware. If the IP does not validate the configuration state stored in persistent memory, upon regaining power or becoming operational again, the IP could be compromised through the activation of an unwanted/harmful configuration.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms
Not OS-Specific

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1304 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1304, Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation, 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 FrameworkNational Institute of Standards and Technology

Address Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restor… during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Integration; recorded impacts include DoS: Instability, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Other), Gain Privileges or Assume Identity, and Bypass Protection Mechanism; the entry maps to CAPEC-176. Use these source-defined anchors to turn CWE-1304 into implementation, review, and verification checks for the affected component.

CWE-1304: Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore OperationMITRE CWE

Triage CWE-1304 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1304, Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation, 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 CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1304

Apply MITRE's full root-cause mapping guidance when using CWE-1304, Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation. 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 GuidanceMITRE CWE

Validate CWE-1304 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1304, Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-1304: Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation?+

CWE-1304: Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product performs a power save/restore operation, but it does not ensure that the integrity of the configuration state is maintained and/or verified between the beginning and ending of the operation. Before powering down, the Intellectual Property (IP) saves current state (S) to persistent storage such as flash or always-on memory in order to optimize the restore operation. During this process, an attacker with access to the persistent storage may alter (S) to a configuration that could potentially modify privileges, disable protections, and/or cause damage to the hardware. If the IP does not validate the configuration state stored in persistent memory, upon regaining power or becoming operational again, the IP could be compromised through the activation of an unwanted/harmful configuration.

What are the security consequences of Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation?+

If exploited, CWE-1304 (Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation) it can compromise Confidentiality and Integrity, leading to outcomes such as DoS: Instability, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Other), Gain Privileges or Assume Identity, Bypass Protection Mechanism and Alter Execution Logic.

How do you prevent or mitigate Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation?+

Recommended mitigations for CWE-1304 include: Inside the IP, incorporate integrity checking on the configuration state via a cryptographic hash. The hash can be protected inside the IP such as by storing it in internal registers which never lose power. Before powering down, the IP performs a hash of the configuration and saves it in these persistent registers. Upon restore, the IP performs a hash of the saved configuration and compares it with the saved hash. If they do not match, then the IP should not trust the configuration. Outside the IP, incorporate integrity checking of the configuration state via a trusted agent. Before powering down, the trusted agent performs a hash of the configuration and saves the hash in persistent storage. Upon restore, the IP requests the trusted agent validate its current configuration. If the configuration hash is invalid, then the IP should not trust the configuration. Outside the IP, incorporate a protected environment that prevents undetected modification of the configuration state by untrusted agents. Before powering down, a trusted agent saves the IP's configuration state in this protected location that only it is privileged to. Upon restore, the trusted agent loads the saved state into the IP.

Which programming languages are affected by Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation?+

CWE-1304 commonly affects 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-1304 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

Advertisement