https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 12:36:44 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-07776 bdu:2024-07776 https://cve.radiocsirt.org/vuln/bdu:2024-07776 https://cve.radiocsirt.org/vuln/euvd-2026-234283 EUVD-2026-234283 https://cve.radiocsirt.org/vuln/euvd-2026-234283 https://cve.radiocsirt.org/vuln/fkie_cve-2022-24790 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-24790 https://cve.radiocsirt.org/vuln/ghsa-h99w-9q5r-gjq9 <p><strong>Affected:</strong> RubyGems: puma</p> <p>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.</p> <p>The following vulnerabilities are addressed by this advisory: - Lenient parsing of `Transfer-Encoding` headers, when unsupported encodings should be rejected and the final encoding must be `chunked`. - Lenient parsing of malformed `Content-Length` headers and chunk sizes, when only digits and hex digits should be allowed. - Lenient parsing of duplicate `Content-Length` headers, when they should be rejected. - Lenient parsing of the ending of chunked segments, when they should end with `\r\n`.</p> <p>The vulnerability has been fixed in 5.6.4 and 4.3.12. When deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.</p> <p>These proxy servers are known to have &#34;good&#34; behavior re: this standard and upgrading Puma may not be necessary. Users are encouraged to validate for themselves.</p> <p>- Nginx (latest) - Apache (latest) - Haproxy 2.5+ - Caddy (latest) - Traefik (latest)</p> <p><strong>Affected:</strong> RubyGems: puma</p> <p>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.</p> <p>The following vulnerabilities are addressed by this advisory: - Lenient parsing of `Transfer-Encoding` headers, when unsupported encodings should be rejected and the final encoding must be `chunked`. - Lenient parsing of malformed `Content-Length` headers and chunk sizes, when only digits and hex digits should be allowed. - Lenient parsing of duplicate `Content-Length` headers, when they should be rejected. - Lenient parsing of the ending of chunked segments, when they should end with `\r\n`.</p> <p>The vulnerability has been fixed in 5.6.4 and 4.3.12. When deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.</p> <p>These proxy servers are known to have &#34;good&#34; behavior re: this standard and upgrading Puma may not be necessary. Users are encouraged to validate for themselves.</p> <p>- Nginx (latest) - Apache (latest) - Haproxy 2.5+ - Caddy (latest) - Traefik (latest)</p> https://cve.radiocsirt.org/vuln/ghsa-h99w-9q5r-gjq9 https://cve.radiocsirt.org/vuln/gsd-2022-24790 gsd-2022-24790 https://cve.radiocsirt.org/vuln/gsd-2022-24790 https://cve.radiocsirt.org/vuln/oesa-2024-2250 <p><strong>Affected:</strong> openEuler:22.03-LTS-SP1: rubygem-puma</p> <p>A simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Security Fix(es): 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.(CVE-2022-24790) 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 known workarounds for this vulnerability.(CVE-2023-40175) Puma is a web server for Ruby/Rack…</p> <p><strong>Affected:</strong> openEuler:22.03-LTS-SP1: rubygem-puma</p> <p>A simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Security Fix(es): 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.(CVE-2022-24790) 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 known workarounds for this vulnerability.(CVE-2023-40175) Puma is a web server for Ruby/Rack…</p> https://cve.radiocsirt.org/vuln/oesa-2024-2250 https://cve.radiocsirt.org/vuln/opensuse-su-2024:12032-1 <p>ruby3.1-rubygem-puma-4-4.3.12-1.1 on GA media</p> <p>ruby3.1-rubygem-puma-4-4.3.12-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:12032-1 https://cve.radiocsirt.org/vuln/rhsa-2022:8532 <p>puma-5.6.4: http request smuggling vulnerabilities</p> <p>puma-5.6.4: http request smuggling vulnerabilities</p> https://cve.radiocsirt.org/vuln/rhsa-2022:8532 https://cve.radiocsirt.org/vuln/suse-su-2022:3338-1 <p>Security update for ardana-ansible, ardana-cobbler, grafana, openstack-heat-templates, openstack-murano, python-Django, rabbitmq-server, rubygem-puma</p> <p>Security update for ardana-ansible, ardana-cobbler, grafana, openstack-heat-templates, openstack-murano, python-Django, rabbitmq-server, rubygem-puma</p> https://cve.radiocsirt.org/vuln/suse-su-2022:3338-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-24790 <p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: puma</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: puma</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-24790 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2109 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Satellite ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Satellite ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2109