CWE-1282 — Assumed-Immutable Data is Stored in Writable Memory
CWE-1282: Assumed-Immutable Data is Stored in Writable Memory
MITRE CWE weakness
| Kind | Weakness |
| Abstraction | Base |
| Status | Incomplete |
| Likelihood of exploit | — |
Description
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.
Common consequences
- Integrity: Varies by Context
Mitigations
Implementation — All immutable code or data should be programmed into ROM or write-once memory.
References
- CWE page: https://cwe.mitre.org/data/definitions/1282.html
- CWE list: https://cwe.mitre.org/data/index.html