Apache Traffic Control Traffic Router TCP Connection Slowloris resource management

Summaryinfo

A vulnerability identified as problematic has been detected in Apache Traffic Control. Affected is an unknown function of the component Traffic Router. This manipulation as part of TCP Connection causes resource management (Slowloris). The identification of this vulnerability is CVE-2017-7670. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Apache Traffic Control (affected version not known). It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Traffic Router. The manipulation as part of a TCP Connection leads to a resource management vulnerability (Slowloris). The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect availability. The summary by CVE is:

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.

The bug was discovered 07/07/2017. The weakness was shared 07/10/2017 (Website). It is possible to read the advisory at lists.apache.org. This vulnerability is known as CVE-2017-7670 since 04/11/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/24/2019).

The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $5k-$25k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• Apache

Name

• Traffic Control

License

• open-source

Website

• Vendor: https://www.apache.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion