RC RANDOM CHAOS

Tor ships emergency relay update against DDoS

Tor shipped relay version 0.4.9.17 as a rapid response to an ongoing DDoS flood of client circuits, with an IPv6 fix flagged as key to relay DoS defenses.

· 2 min read
Tor ships emergency relay update against DDoS

The Tor Project shipped version 0.4.9.17 of its relay software as a rapid response to a DDoS attack that is still running against the network. The release bundles several security fixes, and the project singles out one of them as especially important for relay denial-of-service defenses: it changes how relays handle IPv6.

The attack itself is a flood of client circuits. Tor describes it as massive and ongoing, enough to overwhelm relays across the network and affect most operators. Circuit creation is the expensive part of running a relay. Each new circuit means key exchanges and per-circuit state, so an attacker who can keep opening circuits faster than relays can tear them down ties up CPU and memory without needing to move much traffic. The project says the problem has been difficult to address, which fits: separating a legitimate burst of clients from an adversary spraying circuits is hard when both look like ordinary client behaviour at the protocol level.

The IPv6 fix matters because it is called out by name as the one most relevant to relay DoS defenses. The announcement does not describe the mechanism, so take it as a hardening of IPv6 relay handling under flood conditions rather than a specific documented bug. If you run a relay that listens on IPv6, that is the part of the changelog to read closely.

For relay operators the instruction is short. Upgrade to 0.4.9.17 as soon as you can, and no further action is required after the update installs. The project is clear that this is a first response, not the final one: it is working on additional defenses and expects more releases soon. Treat 0.4.9.17 as the baseline you need right now and plan to apply whatever follows without waiting for a maintenance window.

The announcement is thin on attribution. Tor has not said who is behind the attack or when it started, so there is no indicator set to block and no campaign timeline to map against your own logs. What it does point to is the tor-relays mailing list, where operators are coordinating in the open, and the project is asking operators to keep participating.

The project signed off its announcement by thanking relay operators for helping respond, “Thank you to all… except our attacker(s).”

Share

Keep Reading

Latest on the Wire

Full wire →

New signal daily · RSS

Stay in the loop

New writing delivered when it's ready. No schedule, no spam.