Apache Software Foundation Traffic Control 1.8.1 Release Candidate 0
Approved changes feed: RSS · Atom
cpe:2.3:a:apache:traffic_control:1.8.1:rc0:*:*:*:*:*:*
part: a version: 1.8.1 update: rc0
| Vendor | Apache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95) |
|---|---|
| Product | Traffic Control (e823bf59-9302-59d2-a1a5-fc04830fc269) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:apache/trafficcontrol |
purl2cpe | 2026-06-01 10:14:33.169756 |
pkg:github/apache/trafficcontrol |
purl2cpe | 2026-06-01 10:14:33.169757 |
pkg:pypi/apache-trafficcontrol |
purl2cpe | 2026-06-01 10:14:33.169758 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-7670 |
vulnerable | 2026-06-08 05:10:05.772169 |
Details available
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: 2017-07-10T18:00:00.000Z
Updated: 2024-09-16T17:52:59.730Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.