CWE-1274
Improper Access Control for Volatile Memory Containing Boot Code
Description
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.
{"xhtml:p":["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."]}
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Modify Memory, Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity
Potential Mitigations
Ensure that the design of volatile-memory protections is enough to prevent modification from an adversary or untrusted code.
Test the volatile-memory protections to ensure they are safe from modification or untrusted code.
CVE-2019-2267Locked memory regions may be modified through other interfaces in a secure-boot-loader image due to improper access control.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now