Описание
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 "literal" byte count, which is automatically read by the client'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.
A flaw was found in Net::IMAP, a Ruby library for IMAP client functionality. This vulnerability allows a malicious server to send a large "literal" byte count, causing the client to allocate excessive memory, potentially leading to denial of service (memory exhaustion). This vulnerability could allow an attacker to overload the system's memory, causing performance degradation or crashes when connecting to untrusted or compromised IMAP servers.
Отчет
Within regulated environments, a combination of the following controls acts as a significant barrier to successfully exploiting a resource consumption vulnerability and therefore downgrades the severity of this particular CVE from Moderate to Low. Red Hat applies secure baseline configurations to define memory limits, resource thresholds, and execution parameters across containerized workloads, reducing the risk of uncontrolled resource allocation. Concurrent session controls limit active sessions and resource-heavy operations per user, preventing abuse through amplification or repeated access. System monitoring continuously evaluates memory, CPU, and I/O usage to detect patterns indicative of resource exhaustion or denial-of-service attempts. Memory protection enforces allocation limits and isolated memory spaces to prevent system instability from unbounded requests. Additionally, process isolation ensures workloads remain contained, preventing excessive resource use in one container from affecting others.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Затронутые пакеты
Платформа | Пакет | Состояние | Рекомендация | Релиз |
---|---|---|---|---|
Logging Subsystem for Red Hat OpenShift | openshift-logging/fluentd-rhel8 | Fix deferred | ||
Red Hat 3scale API Management Platform 2 | 3scale-amp-zync-container | Fix deferred | ||
Red Hat Enterprise Linux 10 | ruby | Fix deferred | ||
Red Hat Enterprise Linux 8 | ruby:3.3/ruby | Fix deferred | ||
Red Hat Enterprise Linux 9 | ruby:3.3/ruby | Fix deferred |
Показывать по
Ссылки на источники
Дополнительная информация
Статус:
EPSS
6.5 Medium
CVSS3
Связанные уязвимости
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 "literal" byte count, which is automatically read by the client'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.
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 "literal" byte count, which is automatically read by the client'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.
Net::IMAP implements Internet Message Access Protocol (IMAP) client fu ...
net-imap rubygem vulnerable to possible DoS by memory exhaustion
Уязвимость модуля Net::IMAP языка программирования Ruby, позволяющая нарушителю вызвать отказ в обслуживании
EPSS
6.5 Medium
CVSS3