HTTP Request Smuggling Affecting puma package, versions <5.6.9>=6.0.0, <6.4.3
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUBY-PUMA-8062124
- published20 Sept 2024
- disclosed19 Sept 2024
- creditUnknown
Introduced: 19 Sep 2024
CVE-2024-45614 (opens in a new tab)How to fix?
Upgrade puma to version 5.6.9, 6.4.3 or higher.
Overview
puma is a simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and production environments. It's great for highly concurrent Ruby implementations such as Rubinius and JRuby as well as as providing process worker support to support CRuby well.
Affected versions of this package are vulnerable to HTTP Request Smuggling due to a flaw in the header normalization process. An attacker can overwrite header values set by intermediate proxies by providing the same header as a proxy sent but with underscores in place of hyphens, such as changing X-Forwarded-For to X-Forwarded_For.
Note: It is not recommended to implicitly trust proxy-defined headers for security.
Workaround
When using nginx, this vulnerability can be mitigated by configuring the underscores_in_headers variable to discard headers with underscores.