VulnerableCode Package Details - pkg:gem/gitlab-puma@3.0.0

Search for packages

Vulnerability	Summary	Fixed by
VCID-bk4b-h5hu-2qeq Aliases: CVE-2020-11077 GHSA-w64w-qqph-5gxm	HTTP Smuggling via Transfer-Encoding Header in Puma ### Impact This is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. ### Patches The problem has been fixed in Puma 3.12.6 and Puma 4.3.5. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Puma](https://github.com/puma/puma) * See our [security policy](https://github.com/puma/puma/security/policy)	4.3.5.gitlab.3 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-euqw-bed6-z7d6 Aliases: CVE-2020-11076 GHSA-x7jg-6pwg-fx5h	HTTP Smuggling via Transfer-Encoding Header in Puma ### Impact By using an invalid transfer-encoding header, an attacker could [smuggle an HTTP response.](https://portswigger.net/web-security/request-smuggling) Originally reported by @ZeddYu, who has our thanks for the detailed report. ### Patches The problem has been fixed in Puma 3.12.5 and Puma 4.3.4. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Puma](https://github.com/puma/puma) * See our [security policy](https://github.com/puma/puma/security/policy)	4.3.5.gitlab.3 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-tsrb-zgtb-8ybu Aliases: CVE-2019-16770 GHSA-7xx3-m584-x994	## Keepalive thread overload/DoS ### Impact 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. ### Patches This vulnerability is patched in Puma 4.3.1 and 3.12.2. ### Workarounds Reverse proxies in front of Puma could be configured to always allow less than X keepalive connections to a Puma cluster or process, where X is the number of threads configured in Puma's thread pool. ### For more information If you have any questions or comments about this advisory: * Open an issue at [puma](github.com/puma/puma).	3.12.2 Affected by 0 other vulnerabilities. 4.3.1 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-bk4b-h5hu-2qeq
Aliases:
CVE-2020-11077
GHSA-w64w-qqph-5gxm

HTTP Smuggling via Transfer-Encoding Header in Puma ### Impact This is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. ### Patches The problem has been fixed in Puma 3.12.6 and Puma 4.3.5. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Puma](https://github.com/puma/puma) * See our [security policy](https://github.com/puma/puma/security/policy)

4.3.5.gitlab.3
Affected by 4 other vulnerabilities.

VCID-euqw-bed6-z7d6
Aliases:
CVE-2020-11076
GHSA-x7jg-6pwg-fx5h

HTTP Smuggling via Transfer-Encoding Header in Puma ### Impact By using an invalid transfer-encoding header, an attacker could [smuggle an HTTP response.](https://portswigger.net/web-security/request-smuggling) Originally reported by @ZeddYu, who has our thanks for the detailed report. ### Patches The problem has been fixed in Puma 3.12.5 and Puma 4.3.4. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Puma](https://github.com/puma/puma) * See our [security policy](https://github.com/puma/puma/security/policy)

4.3.5.gitlab.3
Affected by 4 other vulnerabilities.

VCID-tsrb-zgtb-8ybu
Aliases:
CVE-2019-16770
GHSA-7xx3-m584-x994

## Keepalive thread overload/DoS ### Impact 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. ### Patches This vulnerability is patched in Puma 4.3.1 and 3.12.2. ### Workarounds Reverse proxies in front of Puma could be configured to always allow less than X keepalive connections to a Puma cluster or process, where X is the number of threads configured in Puma's thread pool. ### For more information If you have any questions or comments about this advisory: * Open an issue at [puma](github.com/puma/puma).

3.12.2
Affected by 0 other vulnerabilities.

4.3.1
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
This package is not known to fix vulnerabilities.

Vulnerability

Summary

Aliases

This package is not known to fix vulnerabilities.

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-02T12:36:46.147056+00:00	GitLab Importer	Affected by	VCID-euqw-bed6-z7d6	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/gem/gitlab-puma/CVE-2020-11076.yml	38.0.0
2026-04-02T12:36:45.921061+00:00	GitLab Importer	Affected by	VCID-bk4b-h5hu-2qeq	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/gem/gitlab-puma/CVE-2020-11077.yml	38.0.0
2026-04-02T12:36:14.326142+00:00	GitLab Importer	Affected by	VCID-tsrb-zgtb-8ybu	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/gem/gitlab-puma/CVE-2019-16770.yml	38.0.0