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.

Achtergrondinformatie

Introductiemodi

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.

Toepasselijke platforms

Taal

Klasse: Not Language-Specific (Undetermined)

Besturingssystemen

Klasse: Not OS-Specific (Undetermined)

Architecturen

Klasse: Not Architecture-Specific (Undetermined)

Technologieën

Naam: Bus/Interface Hardware (Undetermined)
Klasse: Not Technology-Specific (Undetermined)

Veelvoorkomende gevolgen

Mogelijke risicobeperkingen

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.

Notities kwetsbaarheidsmapping

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

Gerelateerde aanvalspatronen

Notities

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.

Indiening

Wijzigingen