CWEweakness

CWE-1189 Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

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

Description

The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.

Extended description

A System-On-a-Chip (SoC) has a lot of functionality, but it may have a limited number of pins or pads. A pin can only perform one function at a time. However, it can be configured to perform multiple different functions. This technique is called pin multiplexing. Similarly, several resources on the chip may be shared to multiplex and support different features or functions. When such resources are shared between trusted and untrusted agents, untrusted agents may be able to access the assets intended to be accessed only by the trusted agents.

Common consequences

• Access Control: Bypass Protection Mechanism — If resources being used by a trusted user are shared with an untrusted user, the untrusted user may be able to modify the functionality of the shared resource of the trusted user. • Integrity: Quality Degradation — The functionality of the shared resource may be intentionally degraded.

Potential mitigations

• [Architecture and Design] When sharing resources, avoid mixing agents of varying trust levels. Untrusted agents should not share resources with trusted agents.

Detection methods

• Automated Dynamic Analysis: Pre-silicon / post-silicon: Test access to shared systems resources (memory ranges, control registers, etc.) from untrusted software to verify that the assets are not incorrectly exposed to untrusted agents. Note that access to shared resources can be dynamically allowed or revoked based on system flows. Security testing should cover such dynamic shared resource allocation and access control modification flows.

Observed examples

• CVE-2020-8698: Processor has improper isolation of shared resources allowing for information disclosure. • CVE-2019-6260: Baseboard Management Controller (BMC) device implements Advanced High-performance Bus (AHB) bridges that do not require authentication for arbitrary read and write access to the BMC's physical address space from the host, and possibly the network [REF-1138].

Related

Attack pattern · CAPEC (1)

  • CAPEC-124 Shared Resource Manipulation attack pattern

Observed example · CVE (2)

  • CVE-2020-8698 Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information… vulnerability
  • CVE-2019-6260 The ASPEED ast2400 and ast2500 Baseband Management Controller (BMC) hardware and firmware implement Advanced High-performance Bus (AHB)… vulnerability

Child of · CWE (2)

  • CWE-653 Improper Isolation or Compartmentalization weakness
  • CWE-668 Exposure of Resource to Wrong Sphere weakness

Peer of · CWE (1)

  • CWE-1331 Improper Isolation of Shared Resources in Network On Chip (NoC) weakness

Referenced by CAPEC · weakness (1)

  • CAPEC-124 Shared Resource Manipulation attack pattern

Referenced by CVE · weakness (6)

  • CVE-2024-36332 Improper isolation of GPU HW register space could allow a privileged attacker in malicious Guest Virtual Machine (VM) to perform… vulnerability
  • CVE-2025-54518 Improper isolation of shared resources within the CPU operation cache on Zen 2-based products could allow an attacker to corrupt… vulnerability
  • CVE-2025-54514 Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a… vulnerability
  • CVE-2023-31325 Improper isolation of shared resources on System-on-a-chip (SOC) could a privileged attacker to tamper with the contents of the PSP… vulnerability
  • CVE-2023-42667 Improper isolation in the Intel(R) Core(TM) Ultra Processor stream cache mechanism may allow an authenticated user to potentially enable… vulnerability
  • CVE-2023-49141 Improper isolation in some Intel(R) Processors stream cache mechanism may allow an authenticated user to potentially enable escalation of… vulnerability

Referenced by CWE · child of (1)

  • CWE-1303 Non-Transparent Sharing of Microarchitectural Resources weakness

Referenced by CWE · has member (2)

  • CWE-1343 Weaknesses in the 2021 CWE Most Important Hardware Weaknesses List view
  • CWE-1432 Weaknesses in the 2025 CWE Most Important Hardware Weaknesses List view

Referenced by CWE · peer of (1)

  • CWE-1331 Improper Isolation of Shared Resources in Network On Chip (NoC) weakness