Skip to content
Fencer Intel
high 7.5

CVE-2017-7670 json

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

published 2017-07-10 9 y ago modified 2026-06-17 4 mo ago also GHSA-f2wr-c4c4-xjg7 , EUVD-2022-3672

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.7%
EPSS 4.7% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/apache/trafficcontrol 0.0.0-20170531185407-738c10fa1b58, 1.1.4-0.20170531185407-738c10fa1b58, 1.8.1, 2.0.0, 2.1.0-RC1

Exploit prediction

4.67% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/apache/trafficcontrol
>=1.1.4, <1.8.1
>=2.0.0-RC0, <2.0.0
>=2.1.0-RC0, <2.1.0-RC1
<0.0.0-20170531185407-738c10fa1b58
>=0.0.0, <1.1.4-0.20170531185407-738c10fa1b58
1.8.1
2.0.0
2.1.0-RC1
0.0.0-20170531185407-738c10fa1b58
1.1.4-0.20170531185407-738c10fa1b58

Affected products

  • Apache Software Foundation Apache Traffic Control

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.