Unknown vulnerability in a VM template mitigated
THREATQW10
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:3134
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Very Low likelihood = 3 low
An unknown vulnerability is in the VM Template and all machines
Threat actors: Nation State / Law Enforcement Large Corporation Developer error
Mitigations
| Mitigation | Status |
|---|---|
| grsecurity in all Debian templates MITIGQW3 | implemented |
Residual risk
sys-net, sys-firewall and sys-usb use fedora-28 based template VMs (Qubes default)
Where it applies
Applies to 9 components in 3 scenarios.
- sd-app (SecureDrop Client)
- sd-devices (export and print)
- sd-gpg
- sd-log
- sd-proxy
- sd-viewer (disposable VMs)
- sys-firewall
- sys-net
- sys-usb
Workstation: reading submissions · sd-app (SecureDrop Client), sd-proxy, sys-firewall, sys-net, sd-gpg, sd-viewer (disposable VMs), sd-log
Workstation: export and print · sd-app (SecureDrop Client), sd-devices (export and print), sys-usb, sd-viewer (disposable VMs), sd-log
Notes
In scope for audit: No. Existing mitigations: - All SecureDrop-Workstation managed templates use debian-12-minimal with a grsecurity hardened kernel (MITIGQW3).
How this threat is matched
Listed for these components. A boundary covers every component inside it.