Improper Access Control for Volatile Memory Containing Boot Code

Opis

The product conducts a secure-boot process that transfers bootloader code from Non-Volatile Memory (NVM) into Volatile Memory (VM), but it does not have sufficient access control or other protections for the Volatile Memory.

Adversaries could bypass the secure-boot process and execute their own untrusted, malicious boot code.

As a part of a secure-boot process, the read-only-memory (ROM) code for a System-on-Chip (SoC) or other system fetches bootloader code from Non-Volatile Memory (NVM) and stores the code in Volatile Memory (VM), such as dynamic, random-access memory (DRAM) or static, random-access memory (SRAM). The NVM is usually external to the SoC, while the VM is internal to the SoC. As the code is transferred from NVM to VM, it is authenticated by the SoC's ROM code.

Skutki

• Access Control, Integrity

  Modify Memory; Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity

  If the volatile-memory-region protections or access controls are insufficient to prevent modifications from an adversary or untrusted agent, the secure boot may be bypassed or replaced with the execution of an adversary's code.

Zapobieganie

• Architecture and Design

  Ensure that the design of volatile-memory protections is enough to prevent modification from an adversary or untrusted code.

• Testing

  Test the volatile-memory protections to ensure they are safe from modification or untrusted code.

Przykłady podatności

• CVE-2019-2267 Locked memory regions may be modified through other interfaces in a secure-boot-loader image due to improper access control.

Słabość nadrzędna

• CWE-284 Improper Access Control

Kiedy powstaje

• Architecture and Design — This weakness can be introduced during hardware architecture or design but can be identified later during testing.

Dotyczy

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