Missing Support for Security Features in On-chip Fabrics or Buses

Opis

On-chip fabrics or buses either do not support or are not configured to support privilege separation or other security features, such as access control.

Certain on-chip fabrics and buses, especially simple and low-power buses, do not support security features. Apart from data transfer and addressing ports, some fabrics and buses do not have any interfaces to transfer privilege, immutable identity, or any other security attribute coming from the bus master. Similarly, they do not have dedicated signals to transport security-sensitive data from slave to master, such as completions for certain types of transactions. Few other on-chip fabrics and buses support security features and define specific interfaces/signals for transporting security attributes from master to slave or vice-versa. However, including these signals is not mandatory and could be left unconfigured when generating the register-transfer-level (RTL) description for the fabric. Such fabrics or buses should not be used to transport any security attribute coming from the bus master. In general, peripherals with security assets should not be connected to such buses before the transaction from the bus master reaches the bus, unless some form of access control is performed at a fabric bridge or another intermediate module.

Skutki

• Confidentiality, Integrity, Access Control, Availability

  DoS: Crash, Exit, or Restart; Read Memory; Modify Memory

Zapobieganie

• Architecture and Design

  If fabric does not support security features, implement security checks in a bridge or any component that is between the master and the fabric. Alternatively, connect all fabric slaves that do not have any security assets under one such fabric and connect peripherals with security assets to a different fabric that supports security features.

Słabość nadrzędna

• CWE-693 Protection Mechanism Failure

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Processor Hardware, Not Technology-Specific

Źródła

1. AMBA APB Protocol Specification, Version 2.0 — ARM, 2010
2. Open Core Protocol Specification, Release 2.2 — OCP-IP, 2006