Assumed-Immutable Data is Stored in Writable Memory

Opis

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.

Skutki

• Integrity

  Varies by Context

Zapobieganie

• Implementation

  All immutable code or data should be programmed into ROM or write-once memory.

Słabość nadrzędna

• CWE-668 Exposure of Resource to Wrong Sphere

Może prowadzić do

• CWE-471 Modification of Assumed-Immutable Data (MAID)

Kiedy powstaje

• Implementation — Keys, code, configuration settings, and other data should be programmed in write-once or read-only memory instead of writable memory.

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific

Uwagi

This entry is still under development and will continue to see updates and content improvements.

As of CWE 4.3, CWE-1282 and CWE-1233 are being investigated for potential duplication or overlap.