CWE-1192
Weakness AllowedImproper Identifier for IP Block used in System-On-Chip (SOC)
Abstraction: Base · Status: Draft
The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.
Technical nuance
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.
Mapping guidance
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
Content history
updated Description
updated Related_Attack_Patterns
updated Relationships
updated Mapping_Notes
updated Name
updated Weakness_Ordinalities
updated Background_Details, Description, Technical_Nuance
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
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.
CAPEC-113: Interface Manipulation
An adversary manipulates the use or processing of an interface (e.g. Application Programming Interface (API) or System-on-Chip (SoC)) resulting in an adverse impact upon the security of the system implementing the interface. This can allow the adversary to bypass access control and/or execute functionality not intended by the interface implementation, possibly compromising the system which integrates the interface. Interface manipulation can take on a number of forms including forcing the unexpected use of an interface or the use of an interface in an unintended way.