# 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. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jul 2017 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-f2wr-c4c4-xjg7 ## 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 (Uncontrolled Resource Consumption) ## 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 | Ecosystem | 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 | | `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: 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. ## 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](https://insights.sbomify.com/CVE-2024-45387/): Apache Traffic Control: SQL Injection in Traffic Ops endpoint PUT deliveryservice_request_comments (critical 9.9) - [CVE-2021-43350](https://insights.sbomify.com/CVE-2021-43350/): LDAP filter injection vulnerability in Traffic Ops (critical 9.8) - [CVE-2019-12405](https://insights.sbomify.com/CVE-2019-12405/): Improper Authentication in Apache Traffic Control (critical 9.8) - [CVE-2025-61581](https://insights.sbomify.com/CVE-2025-61581/): Apache Traffic Control: ReDoS issue in Traffic Router configuration (high 7.5) - [CVE-2022-23206](https://insights.sbomify.com/CVE-2022-23206/): Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-7670 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2017-7670 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/apache/trafficcontrol (Go): affected all versions; fixed in 0.0.0-20170531185407-738c10fa1b58 - github.com/apache/trafficcontrol (Go): affected all versions; fixed in 0.0.0-20170531185407-738c10fa1b58 - github.com/apache/trafficcontrol (Go): affected from 0.0.0; fixed in 1.1.4-0.20170531185407-738c10fa1b58 - github.com/apache/trafficcontrol (Go): affected from 0.0.0; fixed in 1.1.4-0.20170531185407-738c10fa1b58 - github.com/apache/trafficcontrol (Go): affected from 1.1.4; fixed in 1.8.1 - github.com/apache/trafficcontrol (Go): affected from 1.1.4; fixed in 1.8.1 - github.com/apache/trafficcontrol (Go): affected from 2.0.0-RC0; fixed in 2.0.0 - github.com/apache/trafficcontrol (Go): affected from 2.0.0-RC0; fixed in 2.0.0 - github.com/apache/trafficcontrol (Go): affected from 2.1.0-RC0; fixed in 2.1.0-RC1 - github.com/apache/trafficcontrol (Go): affected from 2.1.0-RC0; fixed in 2.1.0-RC1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-7670/ (Markdown: https://insights.sbomify.com/CVE-2017-7670/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7670 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7670 - OSV: https://osv.dev/vulnerability/CVE-2017-7670 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7670/ Summaries are generated and may contain mistakes; the official description above is the record.