CVE-2017-7670 Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack
Attackers can exhaust the DNS thread pool in Apache Traffic Control Router by holding TCP connections open, causing a denial of service for all DNS requests.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-7670?
CVE-2017-7670 is a high-severity denial of service vulnerability in Apache Traffic Control, published on 10 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-400
Which versions are affected by CVE-2017-7670?
10 open source packages ship an affected version, including github.com/apache/trafficcontrol. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/apache/trafficcontrol Go | All versions | 0.0.0-20170531185407-738c10fa1b58 |
github.com/apache/trafficcontrol Go | All versions | 0.0.0-20170531185407-738c10fa1b58 |
github.com/apache/trafficcontrol Go | From 0.0.0 | 1.1.4-0.20170531185407-738c10fa1b58 |
github.com/apache/trafficcontrol Go | From 0.0.0 | 1.1.4-0.20170531185407-738c10fa1b58 |
github.com/apache/trafficcontrol Go | From 1.1.4 | 1.8.1 |
github.com/apache/trafficcontrol Go | From 1.1.4 | 1.8.1 |
4 more packages
github.com/apache/trafficcontrol Go | From 2.0.0-RC0 | 2.0.0 |
github.com/apache/trafficcontrol Go | From 2.0.0-RC0 | 2.0.0 |
github.com/apache/trafficcontrol Go | From 2.1.0-RC0 | 2.1.0-RC1 |
github.com/apache/trafficcontrol Go | From 2.1.0-RC0 | 2.1.0-RC1 |
Products include Apache Traffic Control.
How do I fix CVE-2017-7670?
Upgrade github.com/apache/trafficcontrol to a fixed version for your release line: 0.0.0-20170531185407-738c10fa1b58, 1.1.4-0.20170531185407-738c10fa1b58, 1.8.1 or 2.0.0.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2017-7670 being exploited?
There is no known exploitation of CVE-2017-7670 in the wild and no public exploit code.
Other vulnerabilities in Apache Traffic Control
- CVE-2024-45387 Apache Traffic Control: SQL Injection in Traffic Ops endpoint PUT deliveryservice_request_comments
- CVE-2021-43350 LDAP filter injection vulnerability in Traffic Ops
- CVE-2019-12405 Improper Authentication in Apache Traffic Control
- CVE-2025-61581 Apache Traffic Control: ReDoS issue in Traffic Router configuration
- CVE-2022-23206 Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth
Sources
Also known as GHSA-f2wr-c4c4-xjg7.