Detalle CWE-1294

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.

Detalles de contexto

Modos de introducción

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.

Plataformas aplicables

Lenguaje

Clase: Not Language-Specific (Undetermined)

Sistemas operativos

Clase: Not OS-Specific (Undetermined)

Arquitecturas

Clase: Not Architecture-Specific (Undetermined)

Tecnologías

Nombre: Bus/Interface Hardware (Undetermined)
Clase: Not Technology-Specific (Undetermined)

Consecuencias comunes

Mitigaciones potenciales

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.

Notas de mapeo de vulnerabilidades

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

Patrones de ataque relacionados

Notas

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.

Envío

Modificaciones