Common Weakness Enumeration

CWE-1317

Weakness Allowed

Improper Access Control in Fabric Bridge

Abstraction: Base · Status: Draft

The product uses a fabric bridge for transactions between two Intellectual Property (IP) blocks, but the bridge does not properly perform the expected privilege, identity, or other access control checks between those IP blocks.

For overall system security, it is important that the access-control privileges associated with any fabric transaction are consistently maintained and applied, even when they are routed or translated by a fabric bridge. A bridge that is connected to a fabric without security features forwards transactions to the slave without checking the privilege level of the master and results in a weakness in SoC access-control security. The same weakness occurs if a bridge does not check the hardware identity of the transaction received from the slave interface of the bridge.

Mapping guidance

This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.

Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Relationships and members
ChildOf: CWE-284 · View CWE-1000
Modes of introduction
Architecture and Design
Implementation
Detection methods

Simulation / Emulation

RTL simulation to ensure that bridge-access controls are implemented properly.

Effectiveness: High

Formal Verification

Formal verification of bridge RTL to ensure that access control cannot be bypassed.

Effectiveness: High

Content history
Submission: Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna · Intel Corporation · 2020-05-19 · CWE 4.3
Contribution: Chen Chen, Rahul Kande, Jeyavijayan Rajendran · Texas A&M University · 2023-06-21 · CWE 4.14

suggested demonstrative example

Contribution: Shaza Zeitouni, Mohamadreza Rostami, Ahmad-Reza Sadeghi · Technical University of Darmstadt · 2023-06-21 · CWE 4.14

suggested demonstrative example

Modification: CWE Content Team · MITRE · 2021-10-28 · CWE 4.6

updated Observed_Examples

Modification: CWE Content Team · MITRE · 2022-04-28 · CWE 4.7

updated Applicable_Platforms

Modification: CWE Content Team · MITRE · 2022-06-28 · CWE 4.8

updated Applicable_Platforms

Modification: CWE Content Team · MITRE · 2022-10-13 · CWE 4.9

updated Demonstrative_Examples, Description, Detection_Factors, Name, Potential_Mitigations

Modification: CWE Content Team · MITRE · 2023-04-27 · CWE 4.11

updated Relationships

Modification: CWE Content Team · MITRE · 2023-06-29 · CWE 4.12

updated Mapping_Notes

Modification: CWE Content Team · MITRE · 2024-02-29 · CWE 4.14

updated Demonstrative_Examples, References

Modification: CWE Content Team · MITRE · 2025-12-11 · CWE 4.19

updated Weakness_Ordinalities

Modification: CWE Content Team · MITRE · 2026-10-28 · CWE 5.0

updated Background_Details, Demonstrative_Examples, Description

0 vulnerabilities reference this CWE, most recent first.

No vulnerabilities reference this CWE.

Mitigation
Architecture and Design

Ensure that the design includes provisions for access-control checks in the bridge for both upstream and downstream transactions.

Mitigation
Implementation

Implement access-control checks in the bridge for both upstream and downstream transactions.

CAPEC-122: Privilege Abuse

An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources.