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