CVE-2017-7670
HIGHCVE-2017-7670 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in github.com/apache/trafficcontrol. O3 Security confirms whether CVE-2017-7670 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack
Blast Radius
github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrolReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/apache/trafficcontrol | ≥ 1.1.4&&< 1.8.1 | 1.8.1 |
| 🐹Go | github.com/apache/trafficcontrol | ≥ 2.0.0-RC0&&< 2.0.0 | 2.0.0 |
| 🐹Go | github.com/apache/trafficcontrol | ≥ 2.1.0-RC0&&< 2.1.0-RC1 | 2.1.0-RC1 |
| 🐹Go | github.com/apache/trafficcontrol | all versions | 0.0.0-20170531185407-738c10fa1b58 |
| 🐹Go | github.com/apache/trafficcontrol | ≥ 0.0.0&&< 1.1.4-0.20170531185407-738c10fa1b58 | 1.1.4-0.20170531185407-738c10fa1b58 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apache/trafficcontrol. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/apache/trafficcontrol to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7670 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2017-7670 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2017-7670. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2017-7670 in your dependencies?
O3 detects CVE-2017-7670 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.