CVE-2017-7670: The Traffic Router component of the incubating Apache Traffic Control project is vulnerable to a Slowloris style Denial of Service attack.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.6% (FIRST EPSS); higher than 91.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/apache/trafficcontrol (Go) 1.1.4-0.20170531185407-738c10fa1b58, 1.8.1, 2.0.0.
Low priority for now. Upgrade to github.com/apache/trafficcontrol (Go) 1.1.4-0.20170531185407-738c10fa1b58, 1.8.1, 2.0.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 10, 2017
- Updated
- Jun 16, 2026
- EPSS
- 4.6% · 91th percentile
- CWE
- CWE-400
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | traffic control | cpe:2.3:a:apache:traffic_control |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Traffic Control
- 1.8.0 incubating, 2.0.0 RC0 incubatingaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache traffic controlup to 1.8.0 inclusive
- apache traffic control1.8.1
- apache traffic control2.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/apache/trafficcontrol | from 0.0.0 · before 1.1.4-0.20170531185407-738c10fa1b58 | 1.1.4-0.20170531185407-738c10fa1b58 |
| Go | github.com/apache/trafficcontrol | from 1.1.4 · before 1.8.1 | 1.8.1 |
| Go | github.com/apache/trafficcontrol | from 2.0.0-RC0 · before 2.0.0 | 2.0.0 |
| Go | github.com/apache/trafficcontrol | from 2.1.0-RC0 · before 2.1.0-RC1 | 2.1.0-RC1 |
| Go | github.com/apache/trafficcontrol | before 0.0.0-20170531185407-738c10fa1b58 | 0.0.0-20170531185407-738c10fa1b58 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-45387Apache Traffic Control: SQL Injection in Traffic Ops endpoint PUT deliveryservice_request_comments55Plan
- CVE-2021-43350LDAP filter injection vulnerability in Traffic Ops40Plan
- CVE-2019-12405Improper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API…40Plan
Published before and after this one in the same product
- Later →CVE-2020-17522Jan 26, 2021 · When ORT (now via atstccfg) generates ip_allow.config files in Apache Traffic Control 3.0.0 to 3.1.0 and 4.0.0 to 4.1.0, those files…24Monitor
- Later →CVE-2021-42009Oct 12, 2021 · Apache Traffic Control Traffic Ops Email Injection Vulnerability18Monitor
- Later →CVE-2022-23206Feb 6, 2022 · Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/apache/trafficcontrol | 0.0.0-20170531185407-738c10fa1b58 | Package registry (OSV) |
| Go:github.com/apache/trafficcontrol | 1.1.4-0.20170531185407-738c10fa1b58 | Package registry (OSV) |
| Go:github.com/apache/trafficcontrol | 1.8.1 | Package registry (OSV) |
| Go:github.com/apache/trafficcontrol | 2.0.0 | Package registry (OSV) |
| Go:github.com/apache/trafficcontrol | 2.1.0-RC1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.