|
| 1 | +### Title |
| 2 | +CVE-2021-39246 - Tor Browser through 10.5.6 and 11.x through 11.0a4 allows a correlation attack excessive verbose logging - Windows, macOS, Linux |
| 3 | + |
| 4 | +### CVE ID |
| 5 | +CVE-2021-39246 |
| 6 | + |
| 7 | +### CVSS Score |
| 8 | +Pending |
| 9 | + |
| 10 | +### Internal ID |
| 11 | +SICK-2021-111 |
| 12 | + |
| 13 | +# Vendor |
| 14 | +Tor |
| 15 | + |
| 16 | +### Product |
| 17 | +Tor Browser on Windows, macOS, Linux |
| 18 | + |
| 19 | +### Product Versions |
| 20 | +10.5.6 and 11.x through 11.0a4 |
| 21 | + |
| 22 | +### Vulnerability Details |
| 23 | + |
| 24 | +Tor Browser through 10.5.6 and 11.x through 11.0a4 allows a correlation attack that can compromise the privacy of visits to v2 onion addresses. If --log or --verbose is used, exact timestamps of these onion-service visits are logged locally, and an attacker might be able to compare them to timestamp data collected by the destination server (or collected by a rogue site within the Tor network). |
| 25 | + |
| 26 | +### Vendor Response |
| 27 | +Open pull request in relation to timestamp logging as v2 will be deprecated soon: |
| 28 | + |
| 29 | +[https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/434](https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/434). |
| 30 | + |
| 31 | +### Proof of Concept |
| 32 | + |
| 33 | +`Tor Browser` latest `10.5.6` is affected. |
| 34 | + |
| 35 | +`Tor Browser` alpha `11.0a4` is affected. |
| 36 | + |
| 37 | +This is because `Tor 0.4.6` introduced a warning every time a client connects to a v2 domain. |
| 38 | + |
| 39 | +See: [https://gitlab.torproject.org/tpo/core/tor/-/commit/5e836eb80c31b97f87b152351b6a7a932aeffaed](https://gitlab.torproject.org/tpo/core/tor/-/commit/5e836eb80c31b97f87b152351b6a7a932aeffaed) |
| 40 | + |
| 41 | +Also see "Log warning when connecting to soon-to-be-deprecated v2 onions." |
| 42 | + |
| 43 | +https://gitlab.torproject.org/tpo/core/tor/-/commit/80c404c4b79f3bcba3fc4585d4c62a62a04f3ed9 |
| 44 | + |
| 45 | + |
| 46 | +```bash |
| 47 | + |
| 48 | +cd /tmp |
| 49 | + |
| 50 | +wget https://www.torproject.org/dist/torbrowser/10.5.6/tor-browser-linux64-10.5.6_en-US.tar.xz |
| 51 | + |
| 52 | +tar -xzvf tor-browser-linux64-10.5.6_en-US.tar.xz |
| 53 | + |
| 54 | +cd /tmp/tor-browser_en-US/ |
| 55 | + |
| 56 | +./start-tor-browser.desktop --verbose |
| 57 | + |
| 58 | +# Launching './Browser/start-tor-browser --detach --verbose'... |
| 59 | + |
| 60 | +``` |
| 61 | + |
| 62 | +Visit any v2 onion site, connection timestamps are logged at the exact moment the server responds. |
| 63 | + |
| 64 | +```console |
| 65 | +Sep 24 16:28:52.000 [warn] Warning! You've just connected to a v2 onion address. These addresses are deprecated for security reasons, and are no longer supported in Tor. Please encourage the site operator to upgrade. For more information see https://blog.torproject.org/v2-deprecation-timeline |
| 66 | + |
| 67 | +Sep 24 16:28:52.000 [warn] Warning! You've just connected to a v2 onion address. These addresses are deprecated for security reasons, and are no longer supported in Tor. Please encourage the site operator to upgrade. For more information see https://blog.torproject.org/v2-deprecation-timeline |
| 68 | + |
| 69 | +Sep 24 16:28:52.000 [warn] Warning! You've just connected to a v2 onion address. These addresses are deprecated for security reasons, and are no longer supported in Tor. Please encourage the site operator to upgrade. For more information see https://blog.torproject.org/v2-deprecation-timeline |
| 70 | + |
| 71 | +Sep 24 16:29:02.000 [warn] Warning! You've just connected to a v2 onion address. These addresses are deprecated for security reasons, and are no longer supported in Tor. Please encourage the site operator to upgrade. For more information see https://blog.torproject.org/v2-deprecation-timeline |
| 72 | + |
| 73 | +``` |
| 74 | + |
| 75 | +#### Disclosure Timeline |
| 76 | +* **2021-07-02** - Researcher discovers vulnerability on bounty platform |
| 77 | +* **2021-07-07** - Report closed as informative |
| 78 | +* **2021-08-17** - Researcher requests CVE |
| 79 | +* **2021-08-17** - Vendor re-notified via sec mailing list, and on bounty platform chat. |
| 80 | +* **2021-09-10** - No response: researcher opens Pull Request to remove timestamps. |
| 81 | +* **2021-09-24** - CVE published |
| 82 | + |
| 83 | +### Links |
| 84 | + |
| 85 | +[https://github.com/sickcodes/security/blob/master/advisories/SICK-2021-111.md](https://github.com/sickcodes/security/blob/master/advisories/SICK-2021-111.md) |
| 86 | + |
| 87 | +[https://sick.codes/sick-2021-111](https://sick.codes/sick-2021-111) |
| 88 | + |
| 89 | +[https://www.privacyaffairs.com/cve-2021-39246-tor-vulnerability/](https://www.privacyaffairs.com/cve-2021-39246-tor-vulnerability/) |
| 90 | + |
| 91 | +[https://gitlab.torproject.org/tpo/core/tor/-/commit/80c404c4b79f3bcba3fc4585d4c62a62a04f3ed9](https://gitlab.torproject.org/tpo/core/tor/-/commit/80c404c4b79f3bcba3fc4585d4c62a62a04f3ed9) |
| 92 | + |
| 93 | +[https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/434](https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/434) |
| 94 | + |
| 95 | +### Researchers |
| 96 | +- *Sick Codes* [https://github.com/sickcodes](https://github.com/sickcodes) || [https://twitter.com/sickcodes](https://twitter.com/sickcodes) |
| 97 | + |
| 98 | +- *Miklos Zoltan* [https://twitter.com/mzb4455](https://twitter.com/mzb4455) || [https://www.privacyaffairs.com/authors/miklos/](https://www.privacyaffairs.com/authors/miklos/) |
| 99 | + |
| 100 | +#### CVE Links |
| 101 | + |
| 102 | +[https://sick.codes/sick-2021-111](https://sick.codes/sick-2021-111) |
| 103 | + |
| 104 | +[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39246](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39246) |
| 105 | + |
| 106 | +[https://nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-39246](https://nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-39246) |
0 commit comments