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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Puma | Puma | * | 4.3.11 (excluding) |
| Puma | Puma | 5.0.0 (including) | 5.6.2 (excluding) |
| Red Hat Satellite 6.11 for RHEL 7 | RedHat | tfm-rubygem-puma-0:5.6.2-1.el7sat | * |
| Red Hat Satellite 6.11 for RHEL 8 | RedHat | rubygem-puma-0:5.6.2-1.el8sat | * |
| Puma | Ubuntu | esm-apps/focal | * |
| Puma | Ubuntu | esm-apps/jammy | * |
| Puma | Ubuntu | focal | * |
| Puma | Ubuntu | impish | * |
| Puma | Ubuntu | jammy | * |
| Puma | Ubuntu | kinetic | * |
| Puma | Ubuntu | trusty | * |
| Puma | Ubuntu | xenial | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.