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.

배경 세부 정보

취약점 도입 방식

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.

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Undetermined)

운영 체제

클래스: Not OS-Specific (Undetermined)

아키텍처

클래스: Not Architecture-Specific (Undetermined)

기술

이름: Bus/Interface Hardware (Undetermined)
클래스: Not Technology-Specific (Undetermined)

일반적인 결과

잠재적 완화 방법

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.

취약점 매핑 메모

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

관련 공격 패턴

메모

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.

제출

수정 사항