https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 20:05:54 +0000 https://vulnerability.circl.lu/vuln/cve-2026-47240 <p><strong>Affected:</strong> ruby net-imap</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a &#34;raw data&#34; argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals. A server without support for non-synchronizing literals may interpret the &#34;+}\r\n&#34; as the end of a malformed command line and respond with a tagged BAD. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed. This affects criteria for #search and #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15.</p> <p><strong>Affected:</strong> ruby net-imap</p> <p>Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a &#34;raw data&#34; argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals. A server without support for non-synchronizing literals may interpret the &#34;+}\r\n&#34; as the end of a malformed command line and respond with a tagged BAD. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed. This affects criteria for #search and #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15.</p> https://vulnerability.circl.lu/vuln/cve-2026-47240 https://vulnerability.circl.lu/vuln/ghsa-8p34-64r3-mwg8 <p><strong>Affected:</strong> RubyGems: net-imap</p> <p>Several Net::IMAP commands accept a &#34;raw data&#34; argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals.</p> <p>### Details</p> <p>Raw data arguments support embedded literal values, both synchronizing and non-synchronizing. Non-synchronizing literals can only be safely sent when the server advertises any of the `LITERAL+`, `LITERAL-`, or `IMAP4rev2` capabilities. But raw data arguments do not verify server support for non-synchronizing literals prior to sending.</p> <p>Servers without support for non-synchronizing literals could handle them in several different ways: If a server sees a `&#34;}\r\n&#34;` byte sequence but can&#39;t parse the literal bytesize, it _may_ cautiously decide to close the connection, blocking any command injection attacks. However, a server without support for non-synchronizing literals may instead interpret the `&#34;+}\r\n&#34;` as the end of a malformed command line and respond with a tagged `BAD`. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed.</p> <p>This affects the following commands&#39; string arguments: * `criteria` for `#search` and `#uid_search` * `search_keys` for `#sort`, `#thread`, `#uid_sort`, and `#uid_thread` * `attr` for `#fetch` and `#uid_fetch`</p> <p>Prior to `net-imap` v0.6.4, v0.5.14, and v0…</p> <p><strong>Affected:</strong> RubyGems: net-imap</p> <p>Several Net::IMAP commands accept a &#34;raw data&#34; argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals.</p> <p>### Details</p> <p>Raw data arguments support embedded literal values, both synchronizing and non-synchronizing. Non-synchronizing literals can only be safely sent when the server advertises any of the `LITERAL+`, `LITERAL-`, or `IMAP4rev2` capabilities. But raw data arguments do not verify server support for non-synchronizing literals prior to sending.</p> <p>Servers without support for non-synchronizing literals could handle them in several different ways: If a server sees a `&#34;}\r\n&#34;` byte sequence but can&#39;t parse the literal bytesize, it _may_ cautiously decide to close the connection, blocking any command injection attacks. However, a server without support for non-synchronizing literals may instead interpret the `&#34;+}\r\n&#34;` as the end of a malformed command line and respond with a tagged `BAD`. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed.</p> <p>This affects the following commands&#39; string arguments: * `criteria` for `#search` and `#uid_search` * `search_keys` for `#sort`, `#thread`, `#uid_sort`, and `#uid_thread` * `attr` for `#fetch` and `#uid_fetch`</p> <p>Prior to `net-imap` v0.6.4, v0.5.14, and v0…</p> https://vulnerability.circl.lu/vuln/ghsa-8p34-64r3-mwg8