CWE-1192 describes a System on a Chip (SoC) that lacks unique, immutable identifiers for its components. It matters to SoC architects and security reviewers working on designs that combine IP from several sources.
How it happens
A SoC contains many IP blocks with different trust requirements. Each one needs an unambiguous identity. MITRE explains that the identity is mostly used to route a transaction or to perform actions such as resetting, retrieving sensitive information, and acting on behalf of something else.
The record names four variants of the weakness:
- Missing: the SoC defines no way to uniquely identify the IP.
- Insufficient: the identifier defends against common attacks but not everything intended.
- Misconfigured: a mechanism exists but is implemented incorrectly.
- Ignored: the SoC or IP does not apply policies or act on the identifier securely.
What an attacker gains
MITRE lists a bypass of a protection mechanism with high impact. If one block can pass itself off as another, rules that depend on who is asking stop meaning anything.
How to find it
The record has no detection methods. In design review, ask for each IP block how it is identified, where that identifier is stored, whether it can be changed, and which policies consume it.
How to fix it
MITRE recommends separation of privilege. Every identity generated in the SoC should be unique and immutable in hardware. What each IP is trusted or not trusted to do should be clearly defined, implemented, configured and tested. If that definition is implemented as a policy, the policy should be immutable or protected with clear authentication and authorization.
Quick check
What is an ignored identifier?
One where the SoC or IP has not applied any policies, or does not act on the identifier securely, so the identity exists but has no effect.
