Szczegóły 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.

Szczegóły kontekstowe

Sposoby wprowadzenia

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.

Odpowiednie platformy

Język

Klasa: Not Language-Specific (Undetermined)

Systemy operacyjne

Klasa: Not OS-Specific (Undetermined)

Architektury

Klasa: Not Architecture-Specific (Undetermined)

Technologie

Nazwa: Bus/Interface Hardware (Undetermined)
Klasa: Not Technology-Specific (Undetermined)

Typowe konsekwencje

Potencjalne środki zaradcze

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.

Uwagi dotyczące mapowania podatności

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

Powiązane wzorce ataków

Notatki

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.

Zgłoszenie

Modyfikacje