Описание
Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2017-7670
- https://github.com/apache/trafficcontrol/pull/633
- https://github.com/apache/trafficcontrol/pull/634
- https://github.com/apache/trafficcontrol/commit/738c10fa1b5861e4cc3944dc7c3065d16f4a708c
- https://lists.apache.org/thread.html/42b207e9f526353b504591684bd02a5e9fcb4b8f28534253d07740a0@%3Cusers.trafficcontrol.apache.org%3E
- https://lists.apache.org/thread.html/bb09fc29e9c2ee85b118a3d5748a8a523d30cf691ff8b606c6a1748c@%3Ccommits.trafficcontrol.apache.org%3E
- https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E
Пакеты
github.com/apache/trafficcontrol
>= 1.1.4, < 1.8.1
1.8.1
github.com/apache/trafficcontrol
>= 2.0.0-RC0, < 2.0.0
2.0.0
github.com/apache/trafficcontrol
= 2.1.0-RC0
2.1.0-RC1
github.com/apache/trafficcontrol
< 0.0.0-20170531185407-738c10fa1b58
0.0.0-20170531185407-738c10fa1b58
github.com/apache/trafficcontrol
>= 0.0.0, < 1.1.4-0.20170531185407-738c10fa1b58
1.1.4-0.20170531185407-738c10fa1b58
Связанные уязвимости
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.