First published: Fri Jul 07 2017(Updated: )
The Traffic Router component of the incubating Apache Traffic Control project is vulnerable to a Slowloris style Denial of Service attack. TCP connections made on the configured DNS port will remain in the `ESTABLISHED` state until the client explicitly closes the connection or Traffic Router is restarted. If connections remain in the `ESTABLISHED` state indefinitely and accumulate in number to match the size of the thread pool dedicated to processing DNS requests, the thread pool becomes exhausted. Once the thread pool is exhausted, Traffic Router is unable to service any DNS request, regardless of transport protocol.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Traffic Control | <=1.8.0 | |
Apache Traffic Control | =1.8.1-rc0 | |
Apache Traffic Control | =2.0.0-rc1 | |
Apache Traffic Control | =2.0.0-rc2 | |
Apache Traffic Control | =2.0.0-rc3 | |
Apache Traffic Control | =2.0.0-rc4 | |
Apache Traffic Control | =2.0.0-rc5 | |
Apache Traffic Control | =2.0.0-rc6 | |
go/github.com/apache/trafficcontrol | =2.1.0-RC0 | 2.1.0-RC1 |
go/github.com/apache/trafficcontrol | >=2.0.0-RC0<2.0.0 | 2.0.0 |
go/github.com/apache/trafficcontrol | >=1.8.0<1.8.1 | 1.8.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.