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

BaseStable

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.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms
Not OS-Specific

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1274 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1274, Improper Access Control for Volatile Memory Containing Boot Code, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Improper Access Control for Volatile Memory Containing Boot Code during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Testing; documented detection approaches include Manual Analysis; recorded impacts include Modify Memory, Execute Unauthorized Code or Commands, and Gain Privileges or Assume Identity. Use these source-defined anchors to turn CWE-1274 into implementation, review, and verification checks for the affected component.

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

Triage CWE-1274 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1274, Improper Access Control for Volatile Memory Containing Boot Code, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1274

Apply MITRE's full root-cause mapping guidance when using CWE-1274, Improper Access Control for Volatile Memory Containing Boot Code. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1274 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1274, Improper Access Control for Volatile Memory Containing Boot Code. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1274: Improper Access Control for Volatile Memory Containing Boot Code?+

CWE-1274: Improper Access Control for Volatile Memory Containing Boot Code is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Access Control for Volatile Memory Containing Boot Code?+

If exploited, CWE-1274 (Improper Access Control for Volatile Memory Containing Boot Code) it can compromise Access Control and Integrity, leading to outcomes such as Modify Memory, Execute Unauthorized Code or Commands and Gain Privileges or Assume Identity.

How do you prevent or mitigate Improper Access Control for Volatile Memory Containing Boot Code?+

Recommended mitigations for CWE-1274 include: 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.

How is Improper Access Control for Volatile Memory Containing Boot Code detected?+

CWE-1274 can be detected using Manual Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Access Control for Volatile Memory Containing Boot Code?+

CWE-1274 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Access Control for Volatile Memory Containing Boot Code?+

MITRE documents real CVEs mapped to CWE-1274, including CVE-2019-2267. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1274 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-1274

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement