CWE-1259 Improper Restriction of Security Token Assignment

The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected, such as improperly restricting the assignment to trusted components.

• Confidentiality, Integrity, Availability, Access Control: Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Modify Memory, Modify Memory, DoS: Crash, Exit, or Restart — An improperly protected Security Token may be able to be programmed by a malicious agent (i.e., the Security Token is mutable) to spoof the action as if it originated from a trusted agent.

• [Architecture and Design, Implementation] Since the Security Tokens are integral for the maintenance of security in an SoC, they need to be protected properly. • Security Token assignment review checks for design inconsistency and common weaknesses. • Security-Token definition and programming flow is tested in both pre-silicon and post-silicon testing.