Key facts
- The Tor Project released Tor version 0.4.9.17, an emergency security update for network relay software, announcing it on November 13.
- This patch strengthens protections against a live distributed denial-of-service attack that swamped relays and hurt most operators.
- A single patch matters most for relay denial-of-service protection involving IPv6.
- A massive flood of client circuits overwhelmed relays across the privacy network, a problem the project described as difficult to address.
Emergency update released The Tor Project released Tor version 0.4.9.17, an emergency security update for network relay software, and announced it on November 13 as a distributed denial-of-service attack overwhelmed relays across the privacy network.
Tor 0.4.9.17 includes a series of security fixes for relay software. The update strengthens protections against a live distributed denial-of-service attack that swamped relays and hurt most operators. A single patch matters most for relay denial-of-service protection involving IPv6. The fix concerns how relays’ built-in denial-of-service protections deal with IPv6.
Guidance for relay operators The Tor Project is urging relay operators to move to 0.4.9.17 immediately. Operators need do nothing else once the update is installed, according to the announcement. The project is also working on additional defenses and expects to issue further releases in the near future.
Dispute over mitigation Whether the patch mitigates the ongoing attack is disputed. The Tor Project says it increases defenses. Operator reports say the disruption continues. “This release comes in rapid response to the ongoing DDoS attack on the network, which has affected most relay operators,” the Tor Project said.
Scale of the attack A massive flood of client circuits overwhelmed relays across the privacy network, a problem the project described as difficult to address. Tor developer David Goulet said in the November 13 announcement that the ongoing DDoS problem is not an easy one to address. Goulet characterized the attack as difficult to manage while relays are overwhelmed by client circuits. “relays across the network are being overwhelmed by a massive flood of client circuits,” Goulet said.
A single relay could face hundreds of circuits per second during the attack, according to Tor developer David Goulet. Goulet said the relays would stay overloaded until the attack ended. Operator feedback indicates the most recent update has not stopped the disruption.
Tor 0.4.9.17 came less than three weeks after Tor 0.4.9.15. Release 0.4.9.15 added three denial-of-service safeguards targeting what the Tor Project called a flood of directory requests.
Operator reports from the field In a November 14 forum post, one relay operator said two of their relays lost HSDir status due to attacks before the update. The same operator said another relay was being targeted when version 0.4.9.17 was released and installed. About ten minutes after upgrading one relay, the assault changed shape, traffic dropped, and the system kept failing to respond. The operator wrote that relay unresponsiveness ultimately caused loss of HSDIR and the attack ceased immediately on loss of HSDIR.
Relay operators say 0.4.9.17 fails to adequately protect HSDir relays. The attacker shifts methods during an active attack. One operator warned the attacker might deanonymize and track onion services, though the Tor Project issued no such warning in its release announcements.
The Tor Project expressed thanks to operators, referenced active talks on its tor-relays mailing list, and requested ongoing support. The relays that make up the Tor network are volunteer-run, meaning the network depends on individuals operating nodes rather than a centralized provider.
The announcement provided no details on who is behind the distributed denial-of-service attacks or when they began.

Join the discussion