1985
[REF-1354]Florian Zaruba. "Fix CWE-1191 in dmi_jtag.sv". 2021. < https://github.com/HACKEVENT/
hackatdac21/blob/58f984d492fdb0369c82ef10fcbbaa4b9850f9fb/piton/design/chip/tile/
ariane/src/riscv-dbg/src/dmi_jtag.sv#L200 >.2023-09-18.
[REF-1353]Florian Zaruba. "Fix CWE-1191 in dmi_jtag.sv". 2021. < https://github.com/HACKEVENT/
hackatdac21/blob/58f984d492fdb0369c82ef10fcbbaa4b9850f9fb/piton/design/chip/tile/
ariane/src/riscv-dbg/src/dmi_jtag.sv#L131 >.2023-09-18.
[REF-1352]Florian Zaruba. "dmi_jtag.sv". 2021. < https://github.com/HACK-EVENT/hackatdac21/
blob/71103971e8204de6a61afc17d3653292517d32bf/piton/design/chip/tile/ariane/src/riscv-dbg/
src/dmi_jtag.sv#L118:L204 >.2023-09-18.
[REF-1364]"dmi_jtag.sv". 2021. < https://github.com/HACK-EVENT/hackatdac21/
blob/71103971e8204de6a61afc17d3653292517d32bf/piton/design/chip/tile/ariane/src/riscv-dbg/
src/dmi_jtag.sv#L82 >.2023-07-15.
[REF-1365]"fix cwe_1205 in dmi_jtag.sv". 2021. < https://github.com/HACK-EVENT/hackatdac21/
blob/c4f4b832218b50c406dbf9f425d3b654117c1355/piton/design/chip/tile/ariane/src/riscv-dbg/src/
dmi_jtag.sv#L158 >.2023-07-22.
CWE-1192: Improper Identifier for IP Block used in System-On-Chip (SOC)
Weakness ID : 1192
Structure : Simple
Abstraction : Base
Description
The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.
Extended Description
A System-on-Chip (SoC) comprises several components (IP) with varied trust requirements. It is
required that each IP is identified uniquely and should distinguish itself from other entities in the
SoC without any ambiguity. The unique secured identity is required for various purposes. Most of
the time the identity is used to route a transaction or perform certain actions, including resetting,
retrieving a sensitive information, and acting upon or on behalf of something else.
There are several variants of this weakness:
• A "missing" identifier is when the SoC does not define any mechanism to uniquely identify the
IP.
• An "insufficient" identifier might provide some defenses - for example, against the most
common attacks - but it does not protect against everything that is intended.
• A "misconfigured" mechanism occurs when a mechanism is available but not implemented
correctly.
• An "ignored" identifier occurs when the SoC/IP has not applied any policies or does not act
upon the identifier securely.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 657 Violation of Secure Design Principles 1446
CWE Version 4.14
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 1986
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Technology : System on Chip (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Access Control Bypass Protection Mechanism High
Potential Mitigations
Phase: Architecture and Design
Strategy = Separation of Privilege
Every identity generated in the SoC should be unique and immutable in hardware. The actions
that an IP is trusted or not trusted should be clearly defined, implemented, configured, and
tested. If the definition is implemented via a policy, then the policy should be immutable or
protected with clear authentication and authorization.
MemberOf Relationships
This MemberOf relationships table shows additional CWE Catgeories and Views that reference this
weakness as a member. This information is often useful in understanding where a weakness fits
within the context of external information sources.
Nature Type ID Name Page
MemberOf 1198 Privilege Separation and Access Control Issues 1194 2470
MemberOf 1418 Comprehensive Categorization: Violation of Secure
Design Principles
1400 2549
Related Attack Patterns
CAPEC-ID Attack Pattern Name
113 Interface Manipulation
CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric
Access Control
Weakness ID : 1193
Structure : Simple
Abstraction : Base
Description
The product enables components that contain untrusted firmware before memory and fabric access
controls have been enabled.
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.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
CWE Version 4.14
CWE-1204: Generation of Weak Initialization Vector (IV)
CWE-1204: Generation of Weak Initialization Vector (IV)