Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Starting in version 0.3.2 and prior to versions 0.3.8, 0.4.19, and 0.5.6, there is a possibility for denial of service by memory exhaustion in net-imap
s response parser. At any time while the client is connected, a malicious server can send can send highly compressed uid-set
data which is automatically read by the clients receiver thread. The response parser uses Range#to_a
to convert the uid-set
data into arrays of integers, with no limitation on the expanded size of the ranges. Versions 0.3.8, 0.4.19, 0.5.6, and higher fix this issue. Additional details for proper configuration of fixed versions and backward compatibility are available in the GitHub Security Advisory.
The product does not properly control the allocation and maintenance of a limited resource.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Red Hat Enterprise Linux 10 | RedHat | ruby-0:3.3.8-10.el10_0 | * |
Red Hat Enterprise Linux 8 | RedHat | ruby:3.3-8100020250414172630.489197e6 | * |
Red Hat Enterprise Linux 9 | RedHat | ruby:3.3-9050020250415095239.9 | * |
RHOL-5.9-RHEL-9 | RedHat | cluster-logging-operator-container-v5.9.13-9 | * |
RHOL-5.9-RHEL-9 | RedHat | cluster-logging-operator-metadata-container-v5.9.13-22 | * |
RHOL-5.9-RHEL-9 | RedHat | log-file-metric-exporter-container-v1.1.0-346 | * |
RHOL-5.9-RHEL-9 | RedHat | logging-eventrouter-container-v0.4.0-363 | * |
RHOL-5.9-RHEL-9 | RedHat | logging-fluentd-container-v5.9.13-5 | * |
RHOL-5.9-RHEL-9 | RedHat | logging-loki-container-v3.3.2-36 | * |
RHOL-5.9-RHEL-9 | RedHat | logging-vector-container-v0.34.1-37 | * |
RHOL-5.9-RHEL-9 | RedHat | logging-view-plugin-container-v5.9.13-7 | * |
RHOL-5.9-RHEL-9 | RedHat | loki-operator-bundle-container-v5.9.13-20 | * |
RHOL-5.9-RHEL-9 | RedHat | loki-operator-container-v5.9.13-9 | * |
RHOL-5.9-RHEL-9 | RedHat | lokistack-gateway-container-v0.1.0-767 | * |
RHOL-5.9-RHEL-9 | RedHat | opa-openshift-container-v0.1.0-383 | * |
Ruby3.2 | Ubuntu | noble | * |
Ruby3.3 | Ubuntu | devel | * |
Ruby3.3 | Ubuntu | oracular | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.