| 1 |
:tocdepth: 3 |
| 2 |
|
| 3 |
============================== |
| 4 |
Cyrus IMAP 3.4.2 Release Notes |
| 5 |
============================== |
| 6 |
|
| 7 |
Download from GitHub: |
| 8 |
|
| 9 |
* https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.4.2/cyrus-imapd-3.4.2.tar.gz |
| 10 |
* https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.4.2/cyrus-imapd-3.4.2.tar.gz.sig |
| 11 |
|
| 12 |
.. _relnotes-3.4.2-changes: |
| 13 |
|
| 14 |
Changes since 3.4.1 |
| 15 |
=================== |
| 16 |
|
| 17 |
Security fixes: |
| 18 |
--------------- |
| 19 |
|
| 20 |
* Fixed :cve:`CVE-2021-33582`: Certain user inputs are used as hash table keys during |
| 21 |
processing. A poorly chosen string hashing algorithm meant that the user |
| 22 |
could control which bucket their data was stored in, allowing a malicious |
| 23 |
user to direct many inputs to a single bucket. Each subsequent insertion to |
| 24 |
the same bucket requires a strcmp of every other entry in it. At tens of |
| 25 |
thousands of entries, each new insertion could keep the CPU busy in a strcmp |
| 26 |
loop for minutes. |
| 27 |
|
| 28 |
The string hashing algorithm has been replaced with a better one, and now |
| 29 |
also uses a random seed per hash table, so malicious inputs cannot be |
| 30 |
precomputed. |
| 31 |
|
| 32 |
Discovered by Matthew Horsfall, Fastmail |
| 33 |
|
| 34 |
Build changes |
| 35 |
------------- |
| 36 |
|
| 37 |
* Fixed :issue:`3527`: build problems when `--without-sieve` configured |
| 38 |
|
| 39 |
Bug fixes |
| 40 |
--------- |
| 41 |
|
| 42 |
* Fixed: missing CY namespace in some DAV responses |
| 43 |
* Fixed: don't allow JMAP uploads if the user does not have r/w access to any |
| 44 |
mailbox/calendar/addressbook |
| 45 |
* Fixed: Email/query sometimes chose the wrong search algorithm |
| 46 |
* Fixed :issue:`3488`: LMTP delivery to shared mailboxes was broken |
| 47 |
* Fixed :issue:`3528`: 'lookup' ACL alone was not allowing IMAP LIST |
| 48 |
* Fixed: RTF message bodies were treated as plain text in search snippets |