From cfdd48d78c4c15ea98805bd0c81f6d00df2df1a8 Mon Sep 17 00:00:00 2001 From: Al Snow <43523+jasnow@users.noreply.github.com> Date: Tue, 17 Nov 2026 10:49:23 -0500 Subject: [PATCH] Two new puma advisories --- gems/puma/GHSA-4v6q-hvv7-49h9.yml | 40 ++++++++++++++++++++++++++ gems/puma/GHSA-rhww-p99c-hgj9.yml | 47 +++++++++++++++++++++++++++++++ 2 files changed, 87 insertions(+) create mode 100644 gems/puma/GHSA-4v6q-hvv7-49h9.yml create mode 100644 gems/puma/GHSA-rhww-p99c-hgj9.yml diff --git a/gems/puma/GHSA-4v6q-hvv7-49h9.yml b/gems/puma/GHSA-4v6q-hvv7-49h9.yml new file mode 100644 index 0000000000..9f8d492737 --- /dev/null +++ b/gems/puma/GHSA-4v6q-hvv7-49h9.yml @@ -0,0 +1,40 @@ +--- +gem: puma +ghsa: 4v6q-hvv7-49h9 +url: https://github.com/puma/puma/security/advisories/GHSA-4v6q-hvv7-49h9 +title: Memory exhaustion with SSL connections +date: 2026-11-16 +description: | + ## Impact + + An unauthenticated client can cause excessive memory use in a Puma + process with an SSL binding, with no limit, until first_data_timeout + closes the connection. + + When OpenSSL hits a fatal error while reading a TLS record, Puma's + MiniSSL C extension checks SSL_want_read() before SSL_get_error(), + so it treats the fatal error as "need more data". Puma then keeps + passing everything the client sends to OpenSSL's input buffer, + which is never read again. + + This is not present on unencrypted (UNIX, TCP) Puma binds. A plaintext + listener closes a connection that sends more than 112 KB without + a complete request. +cvss_v4: 6.9 +patched_versions: + - "~> 7.2.3" + - "~> 8.0.4" + - ">= 8.1.2" +related: + url: + - https://rubygems.org/gems/puma/versions/8.1.2 + - https://github.com/puma/puma/blob/main/History.md#812--2026-11-17 + - https://rubygems.org/gems/puma/versions/8.0.4 + - https://github.com/puma/puma/blob/main/History.md#804--2026-11-17 + - https://rubygems.org/gems/puma/versions/7.2.3 + - https://github.com/puma/puma/blob/main/History.md#723--2026-11-17 + - https://docs.openssl.org/master/man3/SSL_get_error + - https://github.com/puma/puma/security/advisories/GHSA-4v6q-hvv7-49h9 +notes: | + - No CVE from GHSA URL. + - cvss_v4 from GHSA URL. diff --git a/gems/puma/GHSA-rhww-p99c-hgj9.yml b/gems/puma/GHSA-rhww-p99c-hgj9.yml new file mode 100644 index 0000000000..62b2f1011d --- /dev/null +++ b/gems/puma/GHSA-rhww-p99c-hgj9.yml @@ -0,0 +1,47 @@ +--- +gem: puma +platform: jruby +ghsa: rhww-p99c-hgj9 +url: https://github.com/puma/puma/security/advisories/GHSA-rhww-p99c-hgj9 +title: JRuby HTTP parser lets request headers change the request + path and query string, bypassing proxy URL rules +date: 2026-11-16 +description: | + ## Impact + + On JRuby, an unauthenticated client can use request headers to + change Rack env keys that Puma should build only from the request + line, such as QUERY_STRING and PATH_INFO. + + If an application behind a proxy, WAF, or other firewall that makes + decisions based on the request line, this could be abused so that + the app can receive a different path or query. Examples might include + rules like: "only certain IPs can reach /admin", "URLs must be + correctly signed", or "URLs must not match this pattern of a known attacker". + + Examples: + + * GET /search?q=x with Query-String: &role=admin: WAF sees the query + string as q=x, but Rack parses the params as {"q"=>"x, ", "role"=>"admin"}. + + * GET http://example.com/public HTTP/1.1 (absolute-form) with + Request-Path: /admin: WAF or proxy sees /public, but Rack thinks + PATH_INFO is /admin. +cvss_v4: 6.3 +unaffected_versions: + - "< 8.0.0" +patched_versions: + - "~> 8.0.4" + - ">= 8.1.2" +related: + url: + - https://rubygems.org/gems/puma/versions/8.1.2-java + - https://github.com/puma/puma/blob/main/History.md#812--2026-11-17 + - https://rubygems.org/gems/puma/versions/8.0.4-java + - https://github.com/puma/puma/blob/main/History.md#804--2026-11-17 + - https://github.com/puma/puma/pull/3838 + - https://github.com/puma/puma/security/advisories/GHSA-9hf4-67fc-4vf4 + - https://github.com/puma/puma/security/advisories/GHSA-rhww-p99c-hgj9 +notes: | + - No CVE from GHSA URL. + - cvss_v4 from GHSA URL.