Puma Connection Request allocation of resources

Summaryinfo

A vulnerability labeled as problematic has been found in Puma. This impacts an unknown function of the component Connection Handler. Executing a manipulation as part of Request can lead to allocation of resources. This vulnerability is handled as CVE-2019-16770. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Puma (the affected version unknown). It has been declared as problematic. This vulnerability affects an unknown part of the component Connection Handler. The manipulation as part of a Request leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. CVE summarizes:

A poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack. If more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough.

The weakness was released 12/05/2019 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability was named CVE-2019-16770 since 09/24/2019. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.

The vulnerability scanner Nessus provides a plugin with the ID 313807 (Unity Linux 20.1060e / 20.1070e Security Update: rubygem-puma (UTSA-2026-017658)), which helps to determine the existence of the flaw in a target environment.

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

The vulnerability is also documented in the vulnerability database at Tenable (313807). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Puma

Website

• Product: https://github.com/puma/puma/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion