CWE-1193 applies when a product enables components that contain untrusted firmware before memory and fabric access controls have been enabled. It is a boot sequencing flaw in System on a Chip (SoC) designs.
How it happens
After an initial reset, the SoC fabric access controls and other security features must be programmed by trusted firmware as part of boot. If untrusted IP blocks or peripheral microcontrollers are enabled first, the untrusted component can master transactions on the hardware bus. It can then target memory or other assets, because nothing yet says it may not.
What an attacker gains
The record lists a bypass of a protection mechanism, rated high. An untrusted component can master transactions on the hardware bus and target memory or other assets to compromise the SoC boot firmware. Compromising boot firmware is serious because everything after it inherits the damage.
How to find it
The record has no detection methods. Review the boot sequence as a timeline. For each component with untrusted firmware, mark when it is powered and compare that to the moment access controls become active.
How to fix it
MITRE's mitigation is a design rule. The boot sequence should enable fabric access controls and memory protections before enabling third party hardware IPs and peripheral microcontrollers that run untrusted firmware.
Quick check
What can an untrusted core do if it starts first?
It can master transactions on the hardware bus and target memory or other assets to compromise the SoC boot firmware.
