HTTP security configuration vulnerability in Journalist interface mitigated

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

Risk
Medium impact × Low likelihood = 4 medium
After mitigations
Medium impact × Low likelihood = 4 medium (unchanged)

How statuses and scores work

Improper configuration of HTTP headers may lead to application vulnerabilities. They are the first layer of defense and provide defense-in-depth.

Threat actors: Any

Mitigations

Mitigation Status
Only GET, POST, HEAD, (DELETE for JI) HTTP methods allowed MITIG75 implemented
HTTP headers do not expose version information MITIG214 implemented
Journalist interface: X-Content-Type-Options: nosniff MITIG217 implemented
X-XSS-protection, CSP set to self MITIG71 implemented

Where it applies

Applies to 1 component in 2 scenarios.

Source submission · SecureDrop Application
Physical and host layer · SecureDrop Application

Notes

Existing mitigations: Only HTTP GET, POST, HEAD and DELETE are allowed (MITIG75). HTTP headers do not expose version information of system components (MITIG214). X-Content-Type is set to "nosniff" (MITIG217) and Content-Security-Policy is set to "self". X-XSS-Protection is set to "1" (MITIG71). Automated test for mitigation: Yes.

How this threat is matched

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