CPU-based attacks accepted
THREATQW12
· Accepted: The team has decided to live with this risk.
· Defined in catalog.py:3171
- Risk
- High impact × Very Low likelihood = 3 low
- After mitigations
- High impact × Very Low likelihood = 3 low (unchanged)
An attacker with code execution on any VM on the workstation could exploit vulnerabilities in the CPU and obtain code execution in dom0 or another VM.
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| Disabling hyperthreading (done by Qubes) MITIGQW35 | implemented |
Residual risk
Unknown CPU vulnerabilities may expose VMs to side-channel attacks
Where it applies
Applies to 1 component in 1 scenario.
Workstation: boot, provisioning and updates · Workstation hardware
Notes
In scope for audit: No. Existing mitigations: Host (Qubes) and Guest kernels have mitigations=full and nosmt=on (MITIGQW35). Further mitigations: - Disable Hyperthreading at the BIOS-level.
How this threat is matched
Listed for these components. A boundary covers every component inside it.