DNS request to .onion address partially mitigated
THREAT90
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:1570
- Risk
- High impact × Medium likelihood = 9 high
- After mitigations
- High impact × Medium likelihood = 9 high (unchanged)
A user may accidentally copy/paste the onion address into a browser that has not implemented RFC 7686, thus leaking a DNS request from their real IP address to a SecureDrop onion address
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| Firefox does not send DNS requests for onion addresses MITIG100 | implemented |
| .onion addresses not links on the landing page MITIG28 | implemented |
Possible further mitigations
- Chrome does not send DNS requests for onion addresses - is this still not the case? We should push this MITIG101 proposed
- Brave does not send DNS requests for onion addresses - not the case yet but they're working on it MITIG102 proposed
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Source environment
Notes
Existing mitigations: Firefox will not send this request (MITIG100). We instruct news organizations not to put a link to the onion address on their landing page (MITIG28). Further mitigations: Encourage browsers to implement RFC 7686 (MITIG101, MITIG102, maybe other browsers too). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.