CWE-1283: Mutable Attestation or Measurement Reporting Data

Extended Description

A System-on-Chip (SoC) implements secure boot or verified boot. During this boot flow, the SoC often measures the code that it authenticates. The measurement is usually done by calculating the one-way hash of the code binary and extending it to the previous hash. The hashing algorithm should be a Secure One-Way hash function. The final hash, i.e., the value obtained after the completion of the boot flow, serves as the measurement data used in reporting or in attestation. The calculated hash is often stored in registers that can later be read by the party of interest to determine tampering of the boot flow. A common weakness is that the contents in these registers are modifiable by an adversary, thus spoofing the measurement.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1283 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1283, Mutable Attestation or Measurement Reporting Data, 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 Mutable Attestation or Measurement Reporting Data during Architecture and Design

MITRE associates mitigation with Architecture and Design; recorded impacts include Read Memory, and Read Application Data; the entry maps to CAPEC-680. Use these source-defined anchors to turn CWE-1283 into implementation, review, and verification checks for the affected component.

CWE-1283: Mutable Attestation or Measurement Reporting Data — MITRE CWE

Triage CWE-1283 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1283, Mutable Attestation or Measurement Reporting Data, 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-1283

Apply MITRE's full root-cause mapping guidance when using CWE-1283, Mutable Attestation or Measurement Reporting Data. 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-1283 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1283, Mutable Attestation or Measurement Reporting Data. 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-1283: Mutable Attestation or Measurement Reporting Data?+

CWE-1283: Mutable Attestation or Measurement Reporting Data is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary. A System-on-Chip (SoC) implements secure boot or verified boot. During this boot flow, the SoC often measures the code that it authenticates. The measurement is usually done by calculating the one-way hash of the code binary and extending it to the previous hash. The hashing algorithm should be a Secure One-Way hash function. The final hash, i.e., the value obtained after the completion of the boot flow, serves as the measurement data used in reporting or in attestation. The calculated hash is often stored in registers that can later be read by the party of interest to determine tampering of the boot flow. A common weakness is that the contents in these registers are modifiable by an adversary, thus spoofing the measurement.

What are the security consequences of Mutable Attestation or Measurement Reporting Data?+

If exploited, CWE-1283 (Mutable Attestation or Measurement Reporting Data) it can compromise Confidentiality, leading to outcomes such as Read Memory and Read Application Data.

How do you prevent or mitigate Mutable Attestation or Measurement Reporting Data?+

Recommended mitigations for CWE-1283 include: Measurement data should be stored in registers that are read-only or otherwise have access controls that prevent modification by an untrusted agent.

Which programming languages are affected by Mutable Attestation or Measurement Reporting Data?+

CWE-1283 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-1283 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-1283: Mutable Attestation or Measurement Reporting Data

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses