CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control

Extended Description

After initial reset, System-on-Chip (SoC) fabric access controls and other security features need to be programmed by trusted firmware as part of the boot sequence. If untrusted IPs or peripheral microcontrollers are enabled first, then the untrusted component can master transactions on the hardware bus and target memory or other assets to compromise the SoC boot firmware.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1193 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1193, Power-On of Untrusted Execution Core Before Enabling Fabric Access Control, 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 Power-On of Untrusted Execution Core Before Enabling Fabric Access Control during Architecture and Design

MITRE associates mitigation with Architecture and Design; recorded impacts include Bypass Protection Mechanism; the entry maps to CAPEC-1, and CAPEC-180. Use these source-defined anchors to turn CWE-1193 into implementation, review, and verification checks for the affected component.

CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control — MITRE CWE

Triage CWE-1193 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1193, Power-On of Untrusted Execution Core Before Enabling Fabric Access Control, 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-1193

Apply MITRE's full root-cause mapping guidance when using CWE-1193, Power-On of Untrusted Execution Core Before Enabling Fabric Access Control. 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-1193 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1193, Power-On of Untrusted Execution Core Before Enabling Fabric Access Control. 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-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control?+

CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product enables components that contain untrusted firmware before memory and fabric access controls have been enabled. After initial reset, System-on-Chip (SoC) fabric access controls and other security features need to be programmed by trusted firmware as part of the boot sequence. If untrusted IPs or peripheral microcontrollers are enabled first, then the untrusted component can master transactions on the hardware bus and target memory or other assets to compromise the SoC boot firmware.

What are the security consequences of Power-On of Untrusted Execution Core Before Enabling Fabric Access Control?+

If exploited, CWE-1193 (Power-On of Untrusted Execution Core Before Enabling Fabric Access Control) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

How do you prevent or mitigate Power-On of Untrusted Execution Core Before Enabling Fabric Access Control?+

Recommended mitigations for CWE-1193 include: The boot sequence should enable fabric access controls and memory protections before enabling third-party hardware IPs and peripheral microcontrollers that use untrusted firmware.

Which programming languages are affected by Power-On of Untrusted Execution Core Before Enabling Fabric Access Control?+

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

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

A CWE (Common Weakness Enumeration) like CWE-1193 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.

CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Likelihood

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses