Be first to know. Be ready to defend.

Tor ships emergency release 0.4.9.17 as a DDoS floods its relays

Vulnerabilities
Illustration of an onion-routing network of relay nodes being flooded with incoming connections, with a tag reading 'Upgrade to 0.4.9.17'Illustration of an onion-routing network of relay nodes being flooded with incoming connections, with a tag reading 'Upgrade to 0.4.9.17'

The Tor Project has shipped an emergency update, Tor 0.4.9.17, while its network is under a sustained denial-of-service attack. Developer David Goulet announced the release on 13 November, saying the attack has affected most relay operators, whose servers are being overwhelmed by a massive flood of client circuits. It is the project’s second emergency release this month, and the attack is not over.

What the release changes

According to Tor’s official release notes, the most important fix changes how relays count IPv6 clients for their denial-of-service defences.

No extra configuration is needed. Tor says no further action is required after upgrading.

Diagram of the IPv6 fix: before, each IPv6 address in a /64 counted as a separate client, so an attacker rotating addresses stayed under the limit; after, the whole /64 counts as one client and the limit appliesDiagram of the IPv6 fix: before, each IPv6 address in a /64 counted as a separate client, so an attacker rotating addresses stayed under the limit; after, the whole /64 counts as one client and the limit applies

What Tor hasn’t said

Tor has not named an attacker, published traffic volumes or said when the attack began. The release notes describe the bastet problem only as a “potential compromise”, with no further detail. As for when it will end, Tor says it is testing more defences and expects further releases soon.

There is no CVE for these issues. Tor tracks its own security fixes with TROVE identifiers instead.

Who feels it

Journalists, activists, researchers and anyone else who needs to hide their identity or reach blocked sites rely on Tor, as do organisations that publish onion services. Tor’s announcement doesn’t describe the effect on users. The same relays carry everyone’s traffic, though, so expect slower or less reliable connections while the attack goes on.

Keep an eye on the bastet change too. Directory authorities decide which relays the network trusts. Pulling a set of keys before confirming a compromise is a cautious move, and Tor hasn’t said what prompted it.

What to do

  1. Relay operators: upgrade to 0.4.9.17 now. Check your version with tor --version, install the update from your usual package source and follow the tor-relays mailing list for further releases.
  2. Onion service operators: update to the latest stable release and watch the Tor Project forum for new defences.
  3. Tor Browser users: install updates when offered, expect some slowdowns while the attack continues, and only download Tor Browser from the official Tor Project website.
  4. Most security teams: nothing to do. If your organisation runs relays or onion services, make sure whoever looks after them knows about this release.