| 1 |
Cyrus IMAP 3.4.8 Release Notes |
| 2 |
****************************** |
| 3 |
|
| 4 |
Download from GitHub: |
| 5 |
|
| 6 |
* https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus- |
| 7 |
imapd-3.4.8/cyrus-imapd-3.4.8.tar.gz |
| 8 |
|
| 9 |
* https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus- |
| 10 |
imapd-3.4.8/cyrus-imapd-3.4.8.tar.gz.sig |
| 11 |
|
| 12 |
|
| 13 |
Changes since 3.4.7 |
| 14 |
=================== |
| 15 |
|
| 16 |
|
| 17 |
Security fixes |
| 18 |
-------------- |
| 19 |
|
| 20 |
* Fixed CVE-2024-34055: Cyrus-IMAP through 3.8.2 and 3.10.0-beta2 |
| 21 |
allow authenticated attackers to cause unbounded memory allocation |
| 22 |
by sending many LITERALs in a single command. |
| 23 |
|
| 24 |
The IMAP protocol allows for command arguments to be LITERALs of |
| 25 |
negotiated length, and for these the server allocates memory to |
| 26 |
receive the content before instructing the client to proceed. The |
| 27 |
allocated memory is released when the whole command has been |
| 28 |
received and processed. |
| 29 |
|
| 30 |
The IMAP protocol has a number commands that specify an unlimited |
| 31 |
number of arguments, for example SEARCH. Each of these arguments can |
| 32 |
be a LITERAL, for which memory will be allocated and not released |
| 33 |
until the entire command has been received and processed. This can |
| 34 |
run a server out of memory, with varying consequences depending on |
| 35 |
the server's OOM policy. |
| 36 |
|
| 37 |
Discovered by Damian Poddebniak. |
| 38 |
|
| 39 |
Two limits, with corresponding imapd.conf(5) options, have been |
| 40 |
added to address this: |
| 41 |
|
| 42 |
* "maxargssize" (default: unlimited): limits the overall length of a |
| 43 |
single IMAP command. Deployments should configure this to a size |
| 44 |
that suits their system resources and client usage patterns |
| 45 |
|
| 46 |
* "maxliteral" (default: 128K): limits the length of individual IMAP |
| 47 |
LITERALs |
| 48 |
|
| 49 |
Connections sending commands that would exceed these limits will see |
| 50 |
the command fail, or the connection closed, depending on the |
| 51 |
specific context. The error message will contain the "[TOOBIG]" |
| 52 |
response code. |
| 53 |
|
| 54 |
These limits may be set small without affecting message uploads, as |
| 55 |
the APPEND command's message literal is limited by "maxmessagesize", |
| 56 |
not by these new options. |