Malicious VM template mitigated

THREATQW28 · Mitigated: Controls in place bring the risk down to an acceptable level. · Defined in catalog.py:3414

Risk
High impact × Low likelihood = 6 medium
After mitigations
High impact × Low likelihood = 6 medium (unchanged)

How statuses and scores work

An adversary introduces malware in the Qubes VM templates used by the SecureDrop workstation.

Threat actors: Nation State / Law Enforcement Large Corporation Developer error

Mitigations

No mitigations in place.

Residual risk

- Vulnerable packages may be introduced at build time - Templates ship with out of date packages and must be updated.

Where it applies

Applies to 9 components in 3 scenarios.

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
Workstation: boot, provisioning and updates · sd-gpg

Notes

In scope for audit: No. Existing mitigations: Currently use only Qubes-provided templates, and we build our own templates at install-time for Securedrop-workstation (based on Qubes-provided debian-12-minimal). Further mitigations: Switch to qubes-builderv2 for templates.

How this threat is matched

Listed for these components. A boundary covers every component inside it.