LiveActive security incident?Get immediate response
CWE Reference

CWE-1290: Incorrect Decoding of Security Identifiers | Glexia

CWE-1290 (Incorrect Decoding of Security Identifiers) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.

Release 4.20weaknessIncomplete

Glexia's Take · Automated analysis

CWE-1290: Incorrect Decoding of Security Identifiers

Incorrect Decoding of Security Identifiers 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: Resource Consumption (Other),Execute Unauthorized Code or Commands,Gain Privileges or Assume Identity,Quality Degradation

Developer Pattern

CWE-1290 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-1290, 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-1290: Incorrect Decoding of Security Identifiers

The product implements a decoding mechanism to decode certain bus-transaction signals to security identifiers. If the decoding is implemented incorrectly, then untrusted agents can now gain unauthorized access to the asset.

Type
weakness
Abstraction
Base
Status
Incomplete
Source
MITRE CWE definition

Developer And Remediation Guidance

How teams prevent and detect this weakness

Causes

  • The following Pseudo code outlines the process of checking the value of the Security Identifier within the AES_KEY_ACCESS_POLICY register:,Below is a decoder's Pseudo code that only checks for bit [14] of the bus transaction to determine what Security Identifier it must assign.,

Remediation

  • Architecture and Design: Security identifier decoders must be reviewed for design consistency and common weaknesses.
  • Implementation: Access and programming flows must be tested in pre-silicon and post-silicon testing in order to check for this weakness.

Detection

  • Code review
  • SAST
  • DAST
  • Focused regression tests

Mappings

Related CVEs, CWEs, and ATT&CK context

Related CWEs

Related CVEs

Related CVE mappings appear after CVE records are cross-indexed.

Open CWE CVE mapping

ATT&CK Relevance

ATT&CK relevance is shown only when reviewed or responsibly inferred.