HTTP Request Smuggling Affecting rubygem-puma-debuginfo package, versions <0:4.3.12-1.amzn2022.0.1


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.56% (79th 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-AMZN2022-RUBYGEMPUMADEBUGINFO-2998342
  • published29 Aug 2022
  • disclosed30 Mar 2022

Introduced: 30 Mar 2022

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

How to fix?

Upgrade Amazon-Linux:2022 rubygem-puma-debuginfo to version 0:4.3.12-1.amzn2022.0.1 or higher.
This issue was patched in ALAS2022-2022-051.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rubygem-puma-debuginfo package and not the rubygem-puma-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2022 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 Base Scores

version 3.1