CWEweakness

CWE-1315 Improper Setting of Bus Controlling Capability in Fabric End-point

Official page ↗
Abstraction
Base
Structure
Simple
Status
Incomplete
Languages
Not Language-Specific
CWE version
5.0

Description

The bus controller enables bits in the fabric end-point to allow responder devices to control transactions on the fabric.

Extended description

To support reusability, certain fabric interfaces and end points provide a configurable register bit that allows IP blocks connected to the controller to access other peripherals connected to the fabric. This allows the end point to be used with devices that function as a controller or responder. If this bit is set by default in hardware, or if firmware incorrectly sets it later, a device intended to be a responder on a fabric is now capable of controlling transactions to other devices and might compromise system security.

Common consequences

• Access Control: Modify Memory, Read Memory, Bypass Protection Mechanism

Potential mitigations

• [Architecture and Design] For responder devices, the register bit in the fabric end-point that enables the bus controlling capability must be set to 0 by default. This bit should not be set during secure-boot flows. Also, writes to this register must be access-protected to prevent malicious modifications to obtain bus-controlling capability. • [Implementation] For responder devices, the register bit in the fabric end-point that enables the bus controlling capability must be set to 0 by default. This bit should not be set during secure-boot flows. Also, writes to this register must be access-protected to prevent malicious modifications to obtain bus-controlling capability. • [System Configuration] For responder devices, the register bit in the fabric end-point that enables the bus controlling capability must be set to 0 by default. This bit should not be set during secure-boot flows. Also, writes to this register must be access-protected to prevent malicious modifications to obtain bus-controlling capability.

Related

Attack pattern · CAPEC (2)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs attack pattern
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels attack pattern

Child of · CWE (1)

  • CWE-284 Improper Access Control weakness

Referenced by CAPEC · weakness (2)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs attack pattern
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels attack pattern