Ensure the volatile memory is lockable or has locks. Ensure the volatile memory is locked for writes from untrusted agents or adversaries. Try modifying the volatile memory from an untrusted agent, and ensure these writes are dropped.
CWE-1274 Base Estable
Improper Access Control for Volatile Memory Containing Boot Code
This vulnerability occurs when a system's secure-boot process loads bootloader code into volatile memory (like DRAM or SRAM) but fails to properly lock down that memory region afterward. Without…
Definición
What is CWE-1274?
This vulnerability occurs when a system's secure-boot process loads bootloader code into volatile memory (like DRAM or SRAM) but fails to properly lock down that memory region afterward. Without strong access controls, an attacker can modify the boot code in memory, bypassing secure boot and running malicious software.
During a secure boot, the initial read-only memory (ROM) code inside a chip fetches the bootloader from external, non-volatile storage and copies it into internal volatile memory for execution. This code is authenticated as it's loaded. However, if the chip's memory protection unit (MPU) or similar hardware mechanisms don't enforce strict write or execute permissions on this volatile memory region after the transfer, the authenticated code becomes a sitting target.
An attacker with physical or software access can then overwrite this now-unprotected boot code in volatile memory. This allows them to subvert the entire secure-boot chain, replacing the trusted bootloader with their own malicious payload before the system's main processor executes it, completely undermining the device's security foundation.
Impacto en el mundo real
Real-world CVEs caused by CWE-1274
-
Locked memory regions may be modified through other interfaces in a secure-boot-loader image due to improper access control.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
Ejemplo de código vulnerable
Vulnerable Other
A typical SoC secure boot's flow includes fetching the next piece of code (i.e., the boot loader) from NVM (e.g., serial, peripheral interface (SPI) flash), and transferring it to DRAM/SRAM volatile, internal memory, which is more efficient.
The volatile-memory protections or access controls are insufficient. Ejemplo de código seguro
Secure Other
The memory from where the boot loader executes can be modified by an adversary.
A good architecture should define appropriate protections or access controls to prevent modification by an adversary or untrusted agent, once the bootloader is authenticated. What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-1274
- 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.
Señales de detección
How to detect CWE-1274
Analyze the device using the following steps: 1. Identify all fabric master agents that are active during system Boot Flow when initial code is loaded from Non-volatile storage to volatile memory. 1. Identify the volatile memory regions that are used for storing loaded system executable program. 1. During system boot, test programming the identified memory regions in step 2 from all the masters identified in step 1. Only trusted masters should be allowed to write to the memory regions. For example, pluggable device peripherals should not have write access to program load memory regions.
Plexicus detecta automáticamente CWE-1274 y abre un PR de corrección en menos de 60 segundos.
Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.
Preguntas frecuentes ¿Qué es CWE-1274?
¿Qué gravedad tiene CWE-1274?
¿Qué lenguajes o plataformas se ven afectados por CWE-1274?
¿Cómo puedo prevenir CWE-1274?
¿Cómo detecta y corrige Plexicus CWE-1274?
¿Dónde puedo aprender más sobre CWE-1274?
Frequently asked questions
¿Qué es CWE-1274?
This vulnerability occurs when a system's secure-boot process loads bootloader code into volatile memory (like DRAM or SRAM) but fails to properly lock down that memory region afterward. Without strong access controls, an attacker can modify the boot code in memory, bypassing secure boot and running malicious software.
¿Qué gravedad tiene CWE-1274?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-1274?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific.
¿Cómo puedo prevenir CWE-1274?
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.
¿Cómo detecta y corrige Plexicus CWE-1274?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-1274 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-1274?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/1274.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-1274
CWE-284 Padre
Improper Access Control
The software fails to properly limit who can access a resource, allowing unauthorized users or systems to interact with it.
CWE-1191 Hermano
On-Chip Debug and Test Interface With Improper Access Control
This vulnerability occurs when a hardware chip's debug or test interface (like JTAG) lacks proper access controls. Without correct…
CWE-1220 Hermano
Insufficient Granularity of Access Control
This vulnerability occurs when a system's access controls are too broad, allowing unauthorized users or processes to read or modify…
CWE-1224 Hermano
Improper Restriction of Write-Once Bit Fields
This vulnerability occurs when hardware write-once protection mechanisms, often called 'sticky bits,' are incorrectly implemented,…
CWE-1231 Hermano
Improper Prevention of Lock Bit Modification
This vulnerability occurs when hardware or firmware uses a lock bit to protect critical system registers or memory regions, but fails to…
CWE-1233 Hermano
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
This vulnerability occurs when a hardware device uses a lock bit to protect critical configuration registers, but the lock fails to…
CWE-1252 Hermano
CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations
This vulnerability occurs when a CPU's hardware is not set up to enforce a strict separation between writing data to memory and executing…
CWE-1257 Hermano
Improper Access Control Applied to Mirrored or Aliased Memory Regions
This vulnerability occurs when a hardware design maps the same physical memory to multiple addresses (aliasing or mirroring) but fails to…
CWE-1259 Hermano
Improper Restriction of Security Token Assignment
This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly secure its Security Token mechanism. These tokens control which…
Listo cuando tú lo estés
Deja de pagar por desarrollador.
Empieza a cerrar el bucle.
Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.