Category: Security Flow Issues

Draft
Summary

Weaknesses in this category are related to improper design of full-system security flows, including but not limited to secure boot, secure update, and hardware-device attestation.

Membership
IDNameDescription
CWE-1190DMA Device Enabled Too Early in Boot PhaseThe product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract data from or gain privileges on the product.
CWE-1193Power-On of Untrusted Execution Core Before Enabling Fabric Access ControlThe product enables components that contain untrusted firmware before memory and fabric access controls have been enabled.
CWE-1264Hardware Logic with Insecure De-Synchronization between Control and Data ChannelsThe hardware logic for error handling and security checks can incorrectly forward data before the security check is complete.
CWE-1274Improper Access Control for Volatile Memory Containing Boot CodeThe 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.
CWE-1283Mutable Attestation or Measurement Reporting DataThe register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary.
CWE-1310Missing Ability to Patch ROM CodeMissing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.
CWE-1326Missing Immutable Root of Trust in HardwareA missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code.
CWE-1328Security Version Number Mutable to Older VersionsSecurity-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.
CWE-1194Hardware DesignThis view organizes weaknesses around concepts that are frequently used or encountered in hardware design. Accordingly, this view can align closely with the perspectives of designers, manufacturers, educators, and assessment vendors. It provides a variety of categories that are intended to simplify navigation, browsing, and mapping.
Vulnerability Mapping Notes
Usage: Prohibited
Reasons: Category
Rationale:
This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.
Comment:
See member weaknesses of this category.