CWE-1282: Assumed-Immutable Data is Stored in Writable Memory

Extended Description

Security services such as secure boot, authentication of code and data, and device attestation all require assets such as the first stage bootloader, public keys, golden hash digests, etc. which are implicitly trusted. Storing these assets in read-only memory (ROM), fuses, or one-time programmable (OTP) memory provides strong integrity guarantees and provides a root of trust for securing the rest of the system. Security is lost if assets assumed to be immutable can be modified.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1282 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1282, Assumed-Immutable Data is Stored in Writable Memory, 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 Assumed-Immutable Data is Stored in Writable Memory during Implementation

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

CWE-1282: Assumed-Immutable Data is Stored in Writable Memory — MITRE CWE

Triage CWE-1282 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1282, Assumed-Immutable Data is Stored in Writable Memory, 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-1282

Apply MITRE's full root-cause mapping guidance when using CWE-1282, Assumed-Immutable Data is Stored in Writable Memory. 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-1282 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1282, Assumed-Immutable Data is Stored in Writable Memory. 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-1282: Assumed-Immutable Data is Stored in Writable Memory?+

CWE-1282: Assumed-Immutable Data is Stored in Writable Memory is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field. Security services such as secure boot, authentication of code and data, and device attestation all require assets such as the first stage bootloader, public keys, golden hash digests, etc. which are implicitly trusted. Storing these assets in read-only memory (ROM), fuses, or one-time programmable (OTP) memory provides strong integrity guarantees and provides a root of trust for securing the rest of the system. Security is lost if assets assumed to be immutable can be modified.

What are the security consequences of Assumed-Immutable Data is Stored in Writable Memory?+

If exploited, CWE-1282 (Assumed-Immutable Data is Stored in Writable Memory) it can compromise Integrity, leading to outcomes such as Varies by Context.

How do you prevent or mitigate Assumed-Immutable Data is Stored in Writable Memory?+

Recommended mitigations for CWE-1282 include: All immutable code or data should be programmed into ROM or write-once memory.

Which programming languages are affected by Assumed-Immutable Data is Stored in Writable Memory?+

CWE-1282 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-1282 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-1282: Assumed-Immutable Data is Stored in Writable Memory

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses