Application server full of submissions partially mitigated
THREAT108
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:1880
- Risk
- Medium impact × Medium likelihood = 6 medium
- After mitigations
- Medium impact × Medium likelihood = 6 medium (unchanged)
An attacker may exhaust storage space and journalist resources by uploading large useless files
Threat actors: Troll
Mitigations
| Mitigation | Status |
|---|---|
| SecureDrop submissions limited to 500 MB MITIG138 | implemented |
| Source interface only available as a Tor onion service MITIG54 | implemented |
| OSSEC alert sent when server almost full MITIG139 | implemented |
Possible further mitigations
- CAPTCHA for SecureDrop submissions MITIG137 proposed
Residual risk
Admin may miss alert. Automated submissions could occur via bots.
Where it applies
Applies to 1 component in 2 scenarios.
Source submission · Encrypted submission store
Journalist triage · Encrypted submission store
Notes
Existing mitigations: Size limited to 500MB (MITIG138) and through Tor (MITIG54), OSSEC alert is sent to admins when disk space is being exhausted (MITIG139). Further mitigations: Implement CAPTCHA for submissions (MITIG137). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.