CWE-1302: Missing Source Identifier in Entity… | Glexia
CWE-1302 (Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)) weakness overview with consequences, detection methods, mitigations, related…
Glexia's Take · Automated analysis
CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Confidentiality,Integrity,Availability,Access Control: Modify Memory,Read Memory,DoS: Crash, Exit, or Restart,Bypass Protection Mechanism,Execute Unauthorized Code or Commands
Developer Pattern
CWE-1302 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-1302, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
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.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- 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.,The originator should send a transaction with Security Identifier "2" which will allow access to the AES-Key-access register and allow encryption and decryption operations.
Remediation
- Architecture and Design: Transaction details must be reviewed for design inconsistency and common weaknesses.
- Implementation: Security identifier definition and programming flow must be tested in pre-silicon and post-silicon testing.
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.