BaseStable

CWE-1274Improper Access Control for Volatile Memory Containing Boot Code

Category: memory

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.

Common consequences· 1

  • 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.

Potential mitigations· 2

  • [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.

Related CAPEC attack patterns· 2

CAPEC-456CAPEC-679

References

  1. https://cwe.mitre.org/data/definitions/1274.html

Exploits (incoming)2

TypeTargetConfidenceTier
AttackPatternExploitation of Improperly Configured or Implemented Memory Protectionscapec-679100%live
AttackPatternInfected Memorycapec-456100%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
CWE
Improper Prevention of Lock Bit Modification
CWE
Improper Access Control for Register Interface
CWE
Insufficient Granularity of Address Regions Protected by Register Locks
CWE
Improper Restriction of Software Interfaces to Hardware Features
CWE
Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.