MIME hander in sd-app doesn't handle submission format mitigated
THREATQW8
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:3100
- Risk
- High impact × Medium likelihood = 9 high
- After mitigations
- Low impact × Low likelihood = 2 low
The mime type hander does not support the filetype of the submission, and the submission is opened in sd-svs (and not in disposable VM).
Threat actors: Developer error
Mitigations
No mitigations in place.
Possible further mitigations
- Default action for MIME handler in sd-app MITIGQW13 proposed
Related threats
Smaller threats that make up this one:
- Attacker obtains code execution in the sd-app VM THREATQW18 mitigated
Where it applies
Applies to 1 component in 2 scenarios.
Workstation: reading submissions · sd-viewer (disposable VMs)
Workstation: export and print · sd-viewer (disposable VMs)
Notes
Existing mitigations: A list of mime types is specified and the action is to open in a disposable VM. The submissions are hidden on the file system by default (they are in ~/.securedrop-client), reducing the likelyhood that they are opened without the client. The client calls qvm-open-in-dispvm and does not rely on the mime handler in sd-app, but rather the one in sd-viewer. Further mitigations: Don't open files that are not in the mimelist, specify a default action (MITIGQW13).
How this threat is matched
Listed for these components. A boundary covers every component inside it.