[tor-talk] Advisory: Stack disclosure in hidden services logs when SafeLogging disabled
nickm at torproject.org
Mon Sep 18 13:41:26 UTC 2017
[TROVE-2017-008. CVE-2017-0380. Severity: medium]
We have found a possible problem with the code that reports an error
during the construction of an introduction point circuit. Because
of this bug, it is possible that some hidden services will sometimes
write sensitive information into their logs.
This bug can only happen when the SafeLogging option is disabled,
and SafeLogging is enabled by default. If you have not disabled
SafeLogging, then you should be fine.
We are tracking this bug as TROVE-2017-008 and as ticket #23490. It
is also CVE-2017-0380.
1. If you are not running a hidden service, then you don't need
to do anything. This bug does not affect you.
2. If you are running 0.2.5.x, this bug does not affect you: it
first appeared in 0.2.7.2-alpha. Other bugs do affect you,
though: 0.2.5.x is pretty old!
(If you are running 0.2.4, or 0.2.6, or 0.2.7, you should just
upgrade. We aren't supporting those releases.)
3. Make sure that you did not change the value of the SafeLogging
option in your configuration -- or if you did, that you set it
to "1". SafeLogging needs to be turned to "0" or "relay" for
this bug to occur.
4. If you did disable SafeLogging, re-enable it: Set it to 1, and
use a HUP signal to tell Tor to reload its configuration.
5. If you did disable SafeLogging, you should delete any old logs
that were generated with SafeLogging disabled.
(You should be regularly removing old logs anyway, as a best
We found this when we re-added scan-build's dead assignment
checker into the checkers that we run on Tor. Obviously, it's
time to make sure that scan-build gets run more frequently.
There are patches for this issue linked from ticket #23490 on
I will be putting out updated releases today. This bug will be
fixed in 0.2.8.15, 0.2.9.12, 0.3.0.11, 0.3.1.7, and
More information about the tor-talk