https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 07:13:47 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-05909 bdu:2025-05909 https://cve.radiocsirt.org/vuln/bdu:2025-05909 https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2025-43857 <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>### Summary</p> <p>There is a possibility for denial of service by memory exhaustion when `net-imap` reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response.</p> <p>This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname).</p> <p>### Details</p> <p>The IMAP protocol allows &#34;literal&#34; strings to be sent in responses, prefixed with their size in curly braces (e.g. `{1234567890}\r\n`). When `Net::IMAP` receives a response containing a literal string, it calls `IO#read` with that size. When called with a size, `IO#read` immediately allocates memory to buffer the entire string before processing continues. The server does not need to send any more data. There is no limit on the size of literals that will be accepted.</p> <p>### Fix #### Upgrade Users should upgrade to `net-imap` 0.5.7 or later. A configurable `max_response_size` limit has been added to `Net::IMAP`&#39;s response reader. The `max_response_size` limit has also been backported to `net-imap` 0.2.5, 0.3.9, and 0.4.20.</p> <p>To set a global value for `max_response_size`, users must upgrade to `net-imap` ~&gt; 0.4.20, or &gt; 0.5.7.</p> <p>#### Configurat…</p> <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>### Summary</p> <p>There is a possibility for denial of service by memory exhaustion when `net-imap` reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response.</p> <p>This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname).</p> <p>### Details</p> <p>The IMAP protocol allows &#34;literal&#34; strings to be sent in responses, prefixed with their size in curly braces (e.g. `{1234567890}\r\n`). When `Net::IMAP` receives a response containing a literal string, it calls `IO#read` with that size. When called with a size, `IO#read` immediately allocates memory to buffer the entire string before processing continues. The server does not need to send any more data. There is no limit on the size of literals that will be accepted.</p> <p>### Fix #### Upgrade Users should upgrade to `net-imap` 0.5.7 or later. A configurable `max_response_size` limit has been added to `Net::IMAP`&#39;s response reader. The `max_response_size` limit has also been backported to `net-imap` 0.2.5, 0.3.9, and 0.4.20.</p> <p>To set a global value for `max_response_size`, users must upgrade to `net-imap` ~&gt; 0.4.20, or &gt; 0.5.7.</p> <p>#### Configurat…</p> https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2025-43857 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0756 certfr-2025-avi-0756 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0756 https://cve.radiocsirt.org/vuln/euvd-2026-235445 EUVD-2026-235445 https://cve.radiocsirt.org/vuln/euvd-2026-235445 https://cve.radiocsirt.org/vuln/fkie_cve-2025-43857 <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5, there is a possibility for denial of service by memory exhaustion when net-imap reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response. This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname). This issue has been patched in versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5.</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5, there is a possibility for denial of service by memory exhaustion when net-imap reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response. This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname). This issue has been patched in versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-43857 https://cve.radiocsirt.org/vuln/ghsa-j3g3-5qv5-52mj <p><strong>Affected:</strong> RubyGems: net-imap</p> <p>### Summary</p> <p>There is a possibility for denial of service by memory exhaustion when `net-imap` reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response.</p> <p>This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname).</p> <p>### Details</p> <p>The IMAP protocol allows &#34;literal&#34; strings to be sent in responses, prefixed with their size in curly braces (e.g. `{1234567890}\r\n`). When `Net::IMAP` receives a response containing a literal string, it calls `IO#read` with that size. When called with a size, `IO#read` immediately allocates memory to buffer the entire string before processing continues. The server does not need to send any more data. There is no limit on the size of literals that will be accepted.</p> <p>### Fix #### Upgrade Users should upgrade to `net-imap` 0.5.7 or later. A configurable `max_response_size` limit has been added to `Net::IMAP`&#39;s response reader. The `max_response_size` limit has also been backported to `net-imap` 0.2.5, 0.3.9, and 0.4.20.</p> <p>To set a global value for `max_response_size`, users must upgrade to `net-imap` ~&gt; 0.4.20, or &gt; 0.5.7.</p> <p>#### Configurat…</p> <p><strong>Affected:</strong> RubyGems: net-imap</p> <p>### Summary</p> <p>There is a possibility for denial of service by memory exhaustion when `net-imap` reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response.</p> <p>This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname).</p> <p>### Details</p> <p>The IMAP protocol allows &#34;literal&#34; strings to be sent in responses, prefixed with their size in curly braces (e.g. `{1234567890}\r\n`). When `Net::IMAP` receives a response containing a literal string, it calls `IO#read` with that size. When called with a size, `IO#read` immediately allocates memory to buffer the entire string before processing continues. The server does not need to send any more data. There is no limit on the size of literals that will be accepted.</p> <p>### Fix #### Upgrade Users should upgrade to `net-imap` 0.5.7 or later. A configurable `max_response_size` limit has been added to `Net::IMAP`&#39;s response reader. The `max_response_size` limit has also been backported to `net-imap` 0.2.5, 0.3.9, and 0.4.20.</p> <p>To set a global value for `max_response_size`, users must upgrade to `net-imap` ~&gt; 0.4.20, or &gt; 0.5.7.</p> <p>#### Configurat…</p> https://cve.radiocsirt.org/vuln/ghsa-j3g3-5qv5-52mj https://cve.radiocsirt.org/vuln/msrc_cve-2025-43857 msrc_CVE-2025-43857 https://cve.radiocsirt.org/vuln/msrc_cve-2025-43857 https://cve.radiocsirt.org/vuln/oesa-2025-1640 <p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: ruby, openEuler:22.03-LTS-SP4: ruby, openEuler:24.03-LTS: ruby, openEuler:24.03-LTS-SP1: ruby, openEuler:20.03-LTS-SP4: ruby</p> <p>Ruby is a fast and easy interpreted scripting language for object-oriented programming. It has many functions for processing text Files and perform system management tasks (such as Perl). Security Fix(es):</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5, there is a possibility for denial of service by memory exhaustion when net-imap reads server responses. At any time while the client is connected, a malicious server can send can send a &amp;quot;literal&amp;quot; byte count, which is automatically read by the client&amp;apos;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response. This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname). This issue has been patched in versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5.(CVE-2025-43857)</p> <p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: ruby, openEuler:22.03-LTS-SP4: ruby, openEuler:24.03-LTS: ruby, openEuler:24.03-LTS-SP1: ruby, openEuler:20.03-LTS-SP4: ruby</p> <p>Ruby is a fast and easy interpreted scripting language for object-oriented programming. It has many functions for processing text Files and perform system management tasks (such as Perl). Security Fix(es):</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5, there is a possibility for denial of service by memory exhaustion when net-imap reads server responses. At any time while the client is connected, a malicious server can send can send a &amp;quot;literal&amp;quot; byte count, which is automatically read by the client&amp;apos;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response. This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname). This issue has been patched in versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5.(CVE-2025-43857)</p> https://cve.radiocsirt.org/vuln/oesa-2025-1640 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-43857 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: jruby, Ubuntu:16.04:LTS: jruby, Ubuntu:Pro:18.04:LTS: ruby2.5, Ubuntu:18.04:LTS: jruby, Ubuntu:Pro:20.04:LTS: ruby2.7, Ubuntu:20.04:LTS: jruby, Ubuntu:22.04:LTS: ruby3.0, Ubuntu:24.04:LTS: jruby, Ubuntu:24.04:LTS: ruby3.2, Ubuntu:25.10: jruby and 3 more</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5, there is a possibility for denial of service by memory exhaustion when net-imap reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response. This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname). This issue has been patched in versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: jruby, Ubuntu:16.04:LTS: jruby, Ubuntu:Pro:18.04:LTS: ruby2.5, Ubuntu:18.04:LTS: jruby, Ubuntu:Pro:20.04:LTS: ruby2.7, Ubuntu:20.04:LTS: jruby, Ubuntu:22.04:LTS: ruby3.0, Ubuntu:24.04:LTS: jruby, Ubuntu:24.04:LTS: ruby3.2, Ubuntu:25.10: jruby and 3 more</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5, there is a possibility for denial of service by memory exhaustion when net-imap reads server responses. At any time while the client is connected, a malicious server can send can send a &#34;literal&#34; byte count, which is automatically read by the client&#39;s receiver thread. The response reader immediately allocates memory for the number of bytes indicated by the server response. This should not be an issue when securely connecting to trusted IMAP servers that are well-behaved. It can affect insecure connections and buggy, untrusted, or compromised servers (for example, connecting to a user supplied hostname). This issue has been patched in versions 0.5.7, 0.4.20, 0.3.9, and 0.2.5.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-43857 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0914 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Ruby ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Ruby ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0914