CWE-1192: Improper Identifier for IP Block used in System-On-Chip (SOC)
The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.
How it's found
Improper Identifier for IP Block used in System-On-Chip (SOC) is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
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.
Consequences
- Bypass Protection Mechanism
Mitigations
- Architecture and Design: 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.
Where this fits in a TurboPentest engagement
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Frequently asked questions
What is CWE-1192?
The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.
How do you find Improper Identifier for IP Block used in System-On-Chip (SOC)?
Improper Identifier for IP Block used in System-On-Chip (SOC) is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-1192?
Bypass Protection Mechanism
Does TurboPentest test for Improper Identifier for IP Block used in System-On-Chip (SOC)?
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Related CWEs
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a $99 pentest