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

BaseStable

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

View on MITRE
Back to CWE Lookup

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.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-1189: Improper Isolation of Shared Resources on System-on-a-Chip (SoC)?+

CWE-1189: Improper Isolation of Shared Resources on System-on-a-Chip (SoC) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents. 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.

What are the security consequences of Improper Isolation of Shared Resources on System-on-a-Chip (SoC)?+

If exploited, CWE-1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC)) it can compromise Access Control and Integrity, leading to outcomes such as Bypass Protection Mechanism and Quality Degradation.

How do you prevent or mitigate Improper Isolation of Shared Resources on System-on-a-Chip (SoC)?+

Recommended mitigations for CWE-1189 include: When sharing resources, avoid mixing agents of varying trust levels. Untrusted agents should not share resources with trusted agents.

How is Improper Isolation of Shared Resources on System-on-a-Chip (SoC) detected?+

CWE-1189 can be detected using Automated Dynamic Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Isolation of Shared Resources on System-on-a-Chip (SoC)?+

CWE-1189 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Isolation of Shared Resources on System-on-a-Chip (SoC)?+

MITRE documents real CVEs mapped to CWE-1189, including CVE-2020-8698 and CVE-2019-6260. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1189 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More