Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack
Apache Software Foundation Apache Traffic Control
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/apache/trafficcontrol Go |
|
|
Apache Software Foundation Apache Traffic Control
| Product | Affected | Fixed in |
|---|---|---|
| github.com/apache/trafficcontrol Go |
|
|
2.1.0-RC10.0.0-20170531185407-738c10fa1b581.1.4-0.20170531185407-738c10fa1b58The 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.
From the CVE record · apache
Traffic Router leaves TCP connections to its configured DNS port open until the client closes them or Traffic Router restarts. A network attacker can accumulate connections until the DNS request thread pool is exhausted, preventing Traffic Router from serving DNS requests over any transport protocol.
Teams running Apache Traffic Control or the Go package github.com/apache/trafficcontrol should check whether their installed version falls within the affected ranges listed in the advisory.