https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:30:40 +0000 https://cve.radiocsirt.org/vuln/alsa-2025:19719 <p><strong>Affected:</strong> AlmaLinux:8: pcs, AlmaLinux:8: pcs-snmp</p> <p>The pcs packages provide a command-line configuration system for the Pacemaker and Corosync utilities.</p> <p>Security Fix(es):</p> <p>* rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters (CVE-2025-59830) * rack: Rack&#39;s unbounded multipart preamble buffering enables DoS (memory exhaustion) (CVE-2025-61770) * rack: Rack&#39;s multipart parser buffers large non?file fields entirely in memory, enabling DoS (memory exhaustion) (CVE-2025-61771) * rack: Rack memory exhaustion denial of service (CVE-2025-61772) * rubygem-rack: Unbounded read in `Rack::Request` form parsing can lead to memory exhaustion (CVE-2025-61919)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p><strong>Affected:</strong> AlmaLinux:8: pcs, AlmaLinux:8: pcs-snmp</p> <p>The pcs packages provide a command-line configuration system for the Pacemaker and Corosync utilities.</p> <p>Security Fix(es):</p> <p>* rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters (CVE-2025-59830) * rack: Rack&#39;s unbounded multipart preamble buffering enables DoS (memory exhaustion) (CVE-2025-61770) * rack: Rack&#39;s multipart parser buffers large non?file fields entirely in memory, enabling DoS (memory exhaustion) (CVE-2025-61771) * rack: Rack memory exhaustion denial of service (CVE-2025-61772) * rubygem-rack: Unbounded read in `Rack::Request` form parsing can lead to memory exhaustion (CVE-2025-61919)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2025:19719 https://cve.radiocsirt.org/vuln/bdu:2025-13146 bdu:2025-13146 https://cve.radiocsirt.org/vuln/bdu:2025-13146 https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2025-59830 <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>## Summary</p> <p>`Rack::QueryParser` in version `&lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;`, while still splitting on both `&amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.</p> <p>## Details</p> <p>The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;;] */n` splits on both `&amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.</p> <p>Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.</p> <p>## Impact</p> <p>Applications or middleware that directly invoke `Rack::QueryParser` with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector.</p> <p>`Rack::Request`, the primary entry point for typical Rack applications, uses `QueryParser` in a safe way and does not appear vulnerable by default. As such, the severity is considered **low**, with the impact limited to edge cases where `QueryParser` is used directly.</p> <p>## Mitigation</p> <p>* Upgrade to a patched version of Rack where both `&amp;` and `;` are counted consistently toward `params_limit`. * If upgrading is not immediately possible, configure `QueryParser` with an…</p> <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>## Summary</p> <p>`Rack::QueryParser` in version `&lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;`, while still splitting on both `&amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.</p> <p>## Details</p> <p>The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;;] */n` splits on both `&amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.</p> <p>Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.</p> <p>## Impact</p> <p>Applications or middleware that directly invoke `Rack::QueryParser` with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector.</p> <p>`Rack::Request`, the primary entry point for typical Rack applications, uses `QueryParser` in a safe way and does not appear vulnerable by default. As such, the severity is considered **low**, with the impact limited to edge cases where `QueryParser` is used directly.</p> <p>## Mitigation</p> <p>* Upgrade to a patched version of Rack where both `&amp;` and `;` are counted consistently toward `params_limit`. * If upgrading is not immediately possible, configure `QueryParser` with an…</p> https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2025-59830 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/euvd-2026-253472 EUVD-2026-253472 https://cve.radiocsirt.org/vuln/euvd-2026-253472 https://cve.radiocsirt.org/vuln/fkie_cve-2025-59830 <p>Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &amp;, while still splitting on both &amp; and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.</p> <p>Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &amp;, while still splitting on both &amp; and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-59830 https://cve.radiocsirt.org/vuln/ghsa-625h-95r8-8xpm <p><strong>Affected:</strong> RubyGems: rack</p> <p>## Summary</p> <p>`Rack::QueryParser` in version `&lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;`, while still splitting on both `&amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.</p> <p>## Details</p> <p>The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;;] */n` splits on both `&amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.</p> <p>Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.</p> <p>## Impact</p> <p>Applications or middleware that directly invoke `Rack::QueryParser` with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector.</p> <p>`Rack::Request`, the primary entry point for typical Rack applications, uses `QueryParser` in a safe way and does not appear vulnerable by default. As such, the severity is considered **low**, with the impact limited to edge cases where `QueryParser` is used directly.</p> <p>## Mitigation</p> <p>* Upgrade to a patched version of Rack where both `&amp;` and `;` are counted consistently toward `params_limit`. * If upgrading is not immediately possible, configure `QueryParser` with an…</p> <p><strong>Affected:</strong> RubyGems: rack</p> <p>## Summary</p> <p>`Rack::QueryParser` in version `&lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;`, while still splitting on both `&amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.</p> <p>## Details</p> <p>The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;;] */n` splits on both `&amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.</p> <p>Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.</p> <p>## Impact</p> <p>Applications or middleware that directly invoke `Rack::QueryParser` with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector.</p> <p>`Rack::Request`, the primary entry point for typical Rack applications, uses `QueryParser` in a safe way and does not appear vulnerable by default. As such, the severity is considered **low**, with the impact limited to edge cases where `QueryParser` is used directly.</p> <p>## Mitigation</p> <p>* Upgrade to a patched version of Rack where both `&amp;` and `;` are counted consistently toward `params_limit`. * If upgrading is not immediately possible, configure `QueryParser` with an…</p> https://cve.radiocsirt.org/vuln/ghsa-625h-95r8-8xpm https://cve.radiocsirt.org/vuln/opensuse-su-2025:15587-1 <p>ruby3.4-rubygem-rack-2.2-2.2.18-1.1 on GA media</p> <p>ruby3.4-rubygem-rack-2.2-2.2.18-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15587-1 https://cve.radiocsirt.org/vuln/rhsa-2025:19513 <p>rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters rack: Rack&#39;s unbounded multipart preamble buffering enables DoS (memory exhaustion) rack: Rack&#39;s multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion) rack: Rack memory exhaustion denial of service rubygem-rack: Unbounded read in `Rack::Request` form parsing can lead to memory exhaustion</p> <p>rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters rack: Rack&#39;s unbounded multipart preamble buffering enables DoS (memory exhaustion) rack: Rack&#39;s multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion) rack: Rack memory exhaustion denial of service rubygem-rack: Unbounded read in `Rack::Request` form parsing can lead to memory exhaustion</p> https://cve.radiocsirt.org/vuln/rhsa-2025:19513 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-59830 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: ruby-rack, Ubuntu:Pro:16.04:LTS: ruby-rack, Ubuntu:Pro:18.04:LTS: ruby-rack, Ubuntu:Pro:20.04:LTS: ruby-rack, Ubuntu:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack</p> <p>Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &amp;, while still splitting on both &amp; and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: ruby-rack, Ubuntu:Pro:16.04:LTS: ruby-rack, Ubuntu:Pro:18.04:LTS: ruby-rack, Ubuntu:Pro:20.04:LTS: ruby-rack, Ubuntu:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack</p> <p>Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &amp;, while still splitting on both &amp; and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-59830 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2482 <p>Ein Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2482