2085
[REF-1341]Andrew Waterman, Yunsup Lee, Rimas Avižienis, David Patterson and Krste Asanovi#.
"The RISC-V Instruction Set Manual". Volume II: Privileged Architecture. 2016 November 4. <
https://people.eecs.berkeley.edu/~krste/papers/riscv-privileged-v1.9.1.pdf >.2023-06-21.
[REF-1345]Florian Zaruba, Michael Schaffner and Andreas Traber. "csr_regfile.sv". 2019. <
https://github.com/openhwgroup/cva6/blob/7951802a0147aedb21e8f2f6dc1e1e9c4ee857a2/src/
csr_regfile.sv#L868:L871 >.2023-06-21.
CWE-1263: Improper Physical Access Control
Weakness ID : 1263
Structure : Simple
Abstraction : Class
Description
The product is designed with access restricted to certain information, but it does not sufficiently
protect against an unauthorized actor with physical access to these areas.
Extended Description
Sections of a product intended to have restricted access may be inadvertently or intentionally
rendered accessible when the implemented physical protections are insufficient. The specific
requirements around how robust the design of the physical protection mechanism needs to
be depends on the type of product being protected. Selecting the correct physical protection
mechanism and properly enforcing it through implementation and manufacturing are critical to the
overall physical security of the product.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 284 Improper Access Control 680
ParentOf 1243 Sensitive Non-Volatile Information Not Protected During
Debug