HTTP Request Smuggling Affecting ruby2.5-rubygem-puma package, versions <4.3.12-150000.3.9.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.4% (74th percentile)

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-SLES151-RUBY25RUBYGEMPUMA-3043871
  • published14 Oct 2022
  • disclosed13 Oct 2022

Introduced: 13 Oct 2022

CVE-2022-24790  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade SLES:15.1 ruby2.5-rubygem-puma to version 4.3.12-150000.3.9.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ruby2.5-rubygem-puma package and not the ruby2.5-rubygem-puma package as distributed by SLES. See How to fix? for SLES:15.1 relevant fixed versions and status.

Puma is a simple, fast, multi-threaded, parallel HTTP 1.1 server for Ruby/Rack applications. When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma. The vulnerability has been fixed in 5.6.4 and 4.3.12. Users are advised to upgrade as soon as possible. Workaround: when deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.

CVSS Scores

version 3.1