Exposure of Private Information ('Privacy Violation') Affecting rubygem-puma-doc package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.19% (57th 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-RHEL7-RUBYGEMPUMADOC-3375783
  • published26 Mar 2023
  • disclosed11 Feb 2022

Introduced: 11 Feb 2022

CVE-2022-23634  (opens in a new tab)
CWE-359  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 rubygem-puma-doc.

NVD Description

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

Puma is a Ruby/Rack web server built for parallelism. Prior to puma version 5.6.2, puma may not always call close on the response body. Rails, prior to version 7.0.2.2, depended on the response body being closed in order for its CurrentAttributes implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails or Puma version fixes the vulnerability.

CVSS Scores

version 3.1