Source uses tor2web out of scope

THREAT75 · Out of scope: Outside what this threat model covers. · Defined in catalog.py:1321

Risk
High impact × Medium likelihood = 9 high
After mitigations
High impact × Low likelihood = 6 medium

How statuses and scores work

A malicious operator or compromised Tor2Web relay may be in a position to de-anonymise a source or potential source and inspect contents of the communication between Source interface and Source

Threat actors: Nation State / Law Enforcement Large Corporation

Mitigations

Mitigation Status
Warning displayed when Tor2Web headers are present MITIG124 implemented

Possible further mitigations

Residual risk

The message is shown when a user already reached the Tor2Web service, it's already too late. A malicious or compromised Tor2Web relay could log activity and deanonymise the source.

Where it applies

Applies to 1 component in 1 scenario.

Source discovery and OPSEC · Source Tor Browser

Notes

Existing mitigations: Warning message for tor2web user https://github.com/freedomofpress/securedrop/commit/b40ec26ee2f262585b852e6a78e6f8ac98fca24d (MITIG124). Further mitigations: Source guide should be updated to strongly discourage the use of Tor2Web (MITIG125). The confidentiality risk could be mitigated by using HTTPS on the source interface (MITIG6). Automated test for mitigation: No.

How this threat is matched

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