CVE-2017-7670
No exploitation reported by the sources we read.
- Published2017-07-10
- Fixed in2.1.0-RC1 · 2.0.0 · 1.8.1 · 1.1.4-0.20170531185407-738c10fa1b58 · 0.0.0-20170531185407-738c10fa1b58
- WeaknessCWE-400
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2017-07-1018:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-7670?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-7670?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.1 | ≥ 2.1.0-RC0, < 2.1.0-RC1 | 2.1.0-RC1 | OSV |
| 2.0 | ≥ 2.0.0-RC0, < 2.0.0 | 2.0.0 | OSV |
| 1.x | ≥ 1.1.4, < 1.8.1 | 1.8.1 | OSV |
| 1.1 | ≥ 0.0.0, < 1.1.4-0.20170531185407-738c10fa1b58 | 1.1.4-0.20170531185407-738c10fa1b58 | OSV |
| 0.0 | < 0.0.0-20170531185407-738c10fa1b58 | 0.0.0-20170531185407-738c10fa1b58 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.8 | ≤ 1.8.0 | no fix published | NVD |
| 1.8 | = 1.8.1 | no fix published | NVD |
| 2.0 | = 2.0.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update apache/trafficcontrol to 2.1.0-RC1 · 2.0.0 · 1.8.1 · 1.1.4-0.20170531185407-738c10fa1b58 · 0.0.0-20170531185407-738c10fa1b58
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.07.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-400read 2026-10-23
- FIRST EPSSEPSS score4.7 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2017-07-10
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-7670?
Is CVE-2017-7670 actively exploited?
What is the CVSS score for CVE-2017-7670?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.