p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in puma

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für puma: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 15

  1. CVE-2026-47736

    Hoch · CVSS 7.5EPSS 0,35%Keine Korrektur veröffentlicht

    Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion

    Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, when PROXY protocol v1 support is enabled, Puma reads incoming bytes into an internal buffer while waiting for CRLF to determine whether a PROXY v1 line is present, allowing an attacker that continuously sends bytes without CRLF to cause unbounded in-process memory growth and additional CPU cost from repeatedly scanning the growing buffer. This issue is fixed in versions 7.2.1 and 8.0.2.

    Veröffentlicht Aktualisiert
  2. CVE-2026-47737

    Hoch · CVSS 7.5EPSS 0,18%Keine Korrektur veröffentlicht

    Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections

    Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.

    Veröffentlicht Aktualisiert
  3. CVE-2024-45614

    Mittel · CVSS 5.4EPSS 0,64%Korrektur verfügbar

    Header normalization allows for client to clobber proxy set headers in Puma

    Puma is a Ruby/Rack web server built for parallelism. In affected versions clients could clobber values set by intermediate proxies (such as X-Forwarded-For) by providing a underscore version of the same header (X-Forwarded_For). Any users relying on proxy set variables is affected. v6.4.3/v5.6.9 now discards any headers using underscores if the non-underscore version also exists. Effectively, allowing the proxy defined headers to always win. Users are advised to upgrade. Nginx has a underscores_in_headers configuration variable to discard these headers at the proxy level as a mitigation. Any users that are implicitly trusting the proxy defin

    • Auf 6.4.3-1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-21647

    Mittel · CVSS 5.9EPSS 0,96%Korrektur verfügbar

    HTTP Request/Response Smuggling in puma

    Puma is a web server for Ruby/Rack applications built for parallelism. Prior to version 6.4.2, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies in a way that allowed HTTP request smuggling. Fixed versions limits the size of chunk extensions. Without this limit, an attacker could cause unbounded resource (CPU, network bandwidth) consumption. This vulnerability has been fixed in versions 6.4.2 and 5.6.8.

    • Auf 6.4.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-40175

    Hoch · CVSS 7.3EPSS 0,85%Korrektur verfügbar

    Inconsistent Interpretation of HTTP Requests in puma

    Puma is a Ruby/Rack web server built for parallelism. Prior to versions 6.3.1 and 5.6.7, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers in a way that allowed HTTP request smuggling. Severity of this issue is highly dependent on the nature of the web site using puma is. This could be caused by either incorrect parsing of trailing fields in chunked transfer encoding bodies or by parsing of blank/zero-length Content-Length headers. Both issues have been addressed and this vulnerability has been fixed in versions 6.3.1 and 5.6.7. Users are advised to upgrade. There are no kno

    • Auf 5.6.7-1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2022-24790

    Kritisch · CVSS 9.1EPSS 2,19%Korrektur verfügbar

    HTTP Request Smuggling in puma

    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.

    • Auf 5.6.4-1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2022-23634

    Hoch · CVSS 8EPSS 2,11%Korrektur verfügbar

    Information Exposure when using Puma with Rails

    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.

    • Auf 5.6.4-1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2021-41136

    Niedrig · CVSS 3.7EPSS 1,2%Korrektur verfügbar

    Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') in puma

    Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when pr

    • Auf 5.5.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2021-29509

    Hoch · CVSS 7.5EPSS 1,6%Korrektur verfügbar

    Keepalive Connections Causing Denial Of Service in puma

    Puma is a concurrent HTTP 1.1 server for Ruby/Rack applications. The fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster. A `puma` server which received more concurrent `keep-alive` connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections. This

    • Auf 4.3.8-1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2020-11077

    Mittel · CVSS 6.8EPSS 2,88%Korrektur verfügbar

    HTTP Smuggling via Transfer-Encoding Header in Puma

    In Puma (RubyGem) before 4.3.5 and 3.12.6, a client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This is a si

    • Auf 4.3.6-1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2020-5249

    Mittel · CVSS 6.5EPSS 1,57%Korrektur verfügbar

    HTTP Response Splitting (Early Hints) in Puma

    In Puma (RubyGem) before 4.3.3 and 3.12.4, if an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2020-5247, which fixed this vulnerability but only for regular responses. This has been fixed in 4.3.3 and 3.12.4.

    • Auf 3.12.4-1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2020-5247

    Mittel · CVSS 6.5EPSS 2,55%Korrektur verfügbar

    HTTP Response Splitting in Puma

    In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. `CR`, `LF` or`/r`, `/n`) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all he

    • Auf 3.12.4-1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2019-16770

    Mittel · CVSS 5.3EPSS 2,01%Korrektur verfügbar

    Potential DOS attack in Puma

    In Puma before versions 3.12.2 and 4.3.1, a poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack. If more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough. This vulnerability is patched in Puma 4.3.1 and 3.12.2.

    • Auf 3.12.0-4 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →