How severe is CVE-2017-7670?

CVE-2017-7670 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-7670?

CVE-2017-7670 affects the following packages: github.com/apache/trafficcontrol (Go), github.com/apache/trafficcontrol (Go), github.com/apache/trafficcontrol (Go), github.com/apache/trafficcontrol (Go), github.com/apache/trafficcontrol (Go). Ecosystems affected: Go.

How do I fix CVE-2017-7670?

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.

How do I detect CVE-2017-7670 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apache/trafficcontrol, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-7670 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2017-7670 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-7670 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-7670?

CVE-2017-7670 has an EPSS (Exploit Prediction Scoring System) score of 4.7%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-7670?

CVE-2017-7670 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-7670 published, and has it been updated?

CVE-2017-7670 was published on July 10, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2017-7670 — trafficcontrol

HIGHFix: apache/trafficcontrol#633

CVE-2017-7670 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in github.com/apache/trafficcontrol. A fix is available for github.com/apache/trafficcontrol — see the affected versions and patch details below.

Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack

Also known asGHSA-f2wr-c4c4-xjg7

Published

Jul 10, 2017

Updated

Oct 24, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol

Real-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

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/apache/trafficcontrol`	≥ 1.1.4&&< 1.8.1	1.8.1`go get github.com/apache/trafficcontrol@v1.8.1`
🐹Go	`github.com/apache/trafficcontrol`	≥ 2.0.0-RC0&&< 2.0.0	2.0.0`go get github.com/apache/trafficcontrol@v2.0.0`
🐹Go	`github.com/apache/trafficcontrol`	≥ 2.1.0-RC0&&< 2.1.0-RC1	2.1.0-RC1`go get github.com/apache/trafficcontrol@v2.1.0-RC1`
🐹Go	`github.com/apache/trafficcontrol`	all versions	0.0.0-20170531185407-738c10fa1b58`go get github.com/apache/trafficcontrol@v0.0.0-20170531185407-738c10fa1b58`
🐹Go	`github.com/apache/trafficcontrol`	≥ 0.0.0&&< 1.1.4-0.20170531185407-738c10fa1b58	1.1.4-0.20170531185407-738c10fa1b58`go get github.com/apache/trafficcontrol@v1.1.4-0.20170531185407-738c10fa1b58`

Affected Products

1 product · 8 configurations

Application

traffic controlapache

≤ 1.8.0

2 versions

1.8.12.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apache/trafficcontrol, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-7670 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works