Skip to content

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

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Jul 9, 2025

Package

gomod github.com/apache/trafficcontrol (Go)

Affected versions

>= 2.0.0-RC0, < 2.0.0
= 2.1.0-RC0
< 0.0.0-20170531185407-738c10fa1b58
>= 1.1.4, < 1.8.1
>= 0.0.0, < 1.1.4-0.20170531185407-738c10fa1b58

Patched versions

2.0.0
2.1.0-RC1
0.0.0-20170531185407-738c10fa1b58
1.8.1
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.

References

Published by the National Vulnerability Database Jul 10, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Apr 24, 2024
Last updated Jul 9, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(79th percentile)

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Learn more on MITRE.

CVE ID

CVE-2017-7670

GHSA ID

GHSA-f2wr-c4c4-xjg7

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.