Vulnerability introduced to AppVMs via Template dependency partially mitigated

THREATQW58 · Partially mitigated: Some controls are in place, but the risk is still too high. · Defined in catalog.py:3827

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

How statuses and scores work

An upstream package installed in the AppVM template introduces a vulnerability or backdoor into the TemplateVM and AppVMs on which it is based

Threat actors: Any

Mitigations

Mitigation Status
grsecurity in all Debian templates MITIGQW3 implemented
create individual templates for each role in workstation to minimize unnecessary package installs MITIGQW24 implemented

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: grsecurity kernel (MITIGQW3), two distinct templates (MITIGQW24).

How this threat is matched

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