Submission interface is framed mitigated
THREAT32
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:559
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Very Low likelihood = 3 low
An attacker may trick a source into performing actions within the submission interface that may compromise their anonymity or cleartext submissions.
Threat actors: Nation State / Law Enforcement Large Corporation
Mitigations
| Mitigation | Status |
|---|---|
| X-FRAME-OPTIONS DENY HTTP header MITIG79 | implemented |
Possible further mitigations
- e2e encryption MITIG140 proposed
Where it applies
Applies to 1 component in 2 scenarios.
Source submission · Source Interface
Supply chain and dependencies · Source Interface
Notes
Existing mitigations: SecureDrop Source interface uses X-Frame-Options: DENY header (MITIG79). Browser Same Origin Policy should prevent the SecureDrop page from trivial modifications, but more complex attacks are mitigated via the X-Frame-Options: DENY HTTP header. Further mitigations: Sources should be instructed to end-to-end encrypt files to minimize the chance of compromise (MITIG140). Automated test for mitigation: Yes.
How this threat is matched
Listed for these components. A boundary covers every component inside it.