CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)

Extended Description

In a System-On-Chip (SoC), various integrated circuits and hardware engines generate transactions such as to access (reads/writes) assets or perform certain actions (e.g., reset, fetch, compute). A typical transaction is comprised of source identity (to identify the originator of the transaction) and a destination identity (to route the transaction to the respective entity) in addition to much more information in the message. Sometimes the transactions are qualified with a Security Identifier. This Security Identifier helps the destination agent decide on the set of allowed or disallowed actions. A weakness that can exist in such transaction schemes is that the source agent does not consistently include the necessary Security Identifier with the transaction. If the Security Identifier is missing, the destination agent might drop the message (resulting in an inadvertent Denial-of-Service (DoS)) or take inappropriate action by default in its attempt to execute the transaction, resulting in privilege escalation or provision of unintended access.

Code Examples & CVEs

Demonstrative Examples

Consider a system with a register for storing AES key for encryption or decryption. The key is of 128 bits implemented as a set of four 32-bit registers. The key registers are assets, and the register AES_KEY_ACCESS_POLICY is defined to provide the necessary access controls. The access-policy register defines which agents with a security identifier in the transaction can access the AES-key registers. Each bit in this 32-bit register defines a security identifier. There could be a maximum of 32 security identifiers that are allowed accesses to the AES-key registers. The number of the bit when set (i.e., "1") allows for a respective action from an agent whose identity matches the number of the bit; if set to "0" (i.e., Clear), it disallows the respective action to that corresponding agent.

The originator sends a transaction with no security identifier, i.e., meaning the value is "0" or NULL. The AES-Key-access register does not allow the necessary action and drops the transaction because the originator failed to include the required security identifier.

BadOther

Register 								Field description 							 							 								AES_ENC_DEC_KEY_0 								AES key [0:31] for encryption or decryption, Default 0x00000000 							 							 								AES_ENC_DEC_KEY_1 								AES key [32:63] for encryption or decryption, Default 0x00000000 							 							 								AES_ENC_DEC_KEY_2 								AES key [64:95] for encryption or decryption, Default 0x00000000 							 							 								AES_ENC_DEC_KEY_4 								AES key [96:127] for encryption or decryption, Default 0x00000000 							 							 								AES_KEY_ACCESS_POLICY 								[31:0] Default 0x00000004 - agent with Security Identifier "2" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_4 registers

GoodOther

Register 								Field description 							 							 								AES_ENC_DEC_KEY_0 								AES key [0:31] for encryption or decryption, Default 0x00000000 							 							 								AES_ENC_DEC_KEY_1 								AES key [32:63] for encryption or decryption, Default 0x00000000 							 							 								AES_ENC_DEC_KEY_2 								AES key [64:95] for encryption or decryption, Default 0x00000000 							 							 								AES_ENC_DEC_KEY_4 								AES key [96:127] for encryption or decryption, Default 0x00000000 							 							 								AES_KEY_ACCESS_POLICY 								[31:0] Default 0x00000002 - agent with security identifier "2" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_4 registers

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1302 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1302, Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC), throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; recorded impacts include Modify Memory, Read Memory, DoS: Crash, Exit, or Restart, Bypass Protection Mechanism, and Execute Unauthorized Code or Commands; the entry maps to CAPEC-121, and CAPEC-681. Use these source-defined anchors to turn CWE-1302 into implementation, review, and verification checks for the affected component.

CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) — MITRE CWE

Triage CWE-1302 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1302, Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1302

Apply MITRE's full root-cause mapping guidance when using CWE-1302, Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1302 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1302, Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)?+

CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product implements a security identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. A transaction is sent without a security identifier. In a System-On-Chip (SoC), various integrated circuits and hardware engines generate transactions such as to access (reads/writes) assets or perform certain actions (e.g., reset, fetch, compute). A typical transaction is comprised of source identity (to identify the originator of the transaction) and a destination identity (to route the transaction to the respective entity) in addition to much more information in the message. Sometimes the transactions are qualified with a Security Identifier. This Security Identifier helps the destination agent decide on the set of allowed or disallowed actions. A weakness that can exist in such transaction schemes is that the source agent does not consistently include the necessary Security Identifier with the transaction. If the Security Identifier is missing, the destination agent might drop the message (resulting in an inadvertent Denial-of-Service (DoS)) or take inappropriate action by default in its attempt to execute the transaction, resulting in privilege escalation or provision of unintended access.

What are the security consequences of Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)?+

If exploited, CWE-1302 (Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)) it can compromise Confidentiality, Integrity, Availability and Access Control, leading to outcomes such as Modify Memory, Read Memory, DoS: Crash, Exit, or Restart, Bypass Protection Mechanism and Execute Unauthorized Code or Commands.

How do you prevent or mitigate Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)?+

Recommended mitigations for CWE-1302 include: Transaction details must be reviewed for design inconsistency and common weaknesses. Security identifier definition and programming flow must be tested in pre-silicon and post-silicon testing.

Which programming languages are affected by Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)?+

CWE-1302 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1302 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Likelihood

Mitigation Strategies

Phase

Description