CWEweakness

CWE-1303 Non-Transparent Sharing of Microarchitectural Resources

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

Description

Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts.

Extended description

Modern processors use techniques such as out-of-order execution, speculation, prefetching, data forwarding, and caching to increase performance. Details about the implementation of these techniques are hidden from the programmer's view. This is problematic when the hardware implementation of these techniques results in resources being shared across supposedly isolated contexts. Contention for shared resources between different contexts opens covert channels that allow malicious programs executing in one context to recover information from another context. Some examples of shared micro-architectural resources that have been used to leak information between contexts are caches, branch prediction logic, and load or store buffers. Speculative and out-of-order execution provides an attacker with increased control over which data is leaked through the covert channel. If the extent of resource sharing between contexts in the design microarchitecture is undocumented, it is extremely difficult to ensure system assets are protected against disclosure.

Common consequences

• Confidentiality: Read Application Data, Read Memory — Microarchitectural side-channels have been used to leak specific information such as cryptographic keys, and Address Space Layout Randomization (ALSR) offsets as well as arbitrary memory.

Potential mitigations

• [Architecture and Design] Microarchitectural covert channels can be addressed using a mixture of hardware and software mitigation techniques. These include partitioned caches, new barrier and flush instructions, and disabling high resolution performance counters and timers. • [Requirements] Microarchitectural covert channels can be addressed using a mixture of hardware and software mitigation techniques. These include partitioned caches, new barrier and flush instructions, and disabling high resolution performance counters and timers.

Related

Attack pattern · CAPEC (1)

  • CAPEC-663 Exploitation of Transient Instruction Execution attack pattern

Child of · CWE (2)

  • CWE-1189 Improper Isolation of Shared Resources on System-on-a-Chip (SoC) weakness
  • CWE-203 Observable Discrepancy weakness

Referenced by CAPEC · weakness (1)

  • CAPEC-663 Exploitation of Transient Instruction Execution attack pattern

Referenced by CVE · weakness (5)

  • CVE-2026-59130 No cwe for this issue in AMD Zen allows an authorized attacker to disclose information locally. vulnerability
  • CVE-2026-59131 No cwe for this issue in AMD Zen allows an authorized attacker to disclose information locally. vulnerability
  • CVE-2023-38575 Non-transparent sharing of return predictor targets between contexts in some Intel(R) Processors may allow an authorized user to… vulnerability
  • CVE-2023-40540 Non-Transparent Sharing of Microarchitectural Resources in some Intel(R) NUC BIOS firmware may allow a privileged user to potentially… vulnerability
  • CVE-2023-1998 The Linux kernel allows userspace processes to enable mitigations by calling prctl with PR_SET_SPECULATION_CTRL which disables the… vulnerability