CWE-1294 Detail

The System-on-Chip (SoC) implements a Security Identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Identifiers are not correctly implemented.

Background Details

Modes Of Introduction

Architecture and Design : Such issues could be introduced during hardware architecture and design, then identified later during Testing or System Configuration phases.
Implementation : Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.

Piattaforme applicabili

Linguaggio

Classe: Not Language-Specific (Undetermined)

Sistemi operativi

Classe: Not OS-Specific (Undetermined)

Architetture

Classe: Not Architecture-Specific (Undetermined)

Tecnologie

Nome: Bus/Interface Hardware (Undetermined)
Classe: Not Technology-Specific (Undetermined)

Conseguenze comuni

Potential Mitigations

Phases : Architecture and Design
Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.
Phases : Implementation
Access and programming flows must be tested in pre-silicon and post-silicon testing.

Note sulla mappatura delle vulnerabilità

Giustificazione : This CWE entry is a Class and might have Base-level children that would be more appropriate
Commento : Examine children of this entry to see if there is a better fit

Pattern di attacco correlati

Note

This entry is still under development and will continue to see updates and content improvements.
Research could be conducted to better understand the different kinds of weaknesses that constitute an "insecure" Security Identifier mechanism. See Technical_Nuance.

Invio

Modifiche