Dovecot v2.3.15 released
Hi,
Here's a new release with some security fixes and quite a lot of other changes as well.
https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz <https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz> https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz.sig <https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz.sig>
Binary packages in https://repo.dovecot.org/ <https://repo.dovecot.org/> Docker images in https://hub.docker.com/r/dovecot/dovecot <https://hub.docker.com/r/dovecot/dovecot>
- CVE-2021-29157: Dovecot does not correctly escape kid and azp fields in JWT tokens. This may be used to supply attacker controlled keys to validate tokens, if attacker has local access.
- CVE-2021-33515: On-path attacker could have injected plaintext commands before STARTTLS negotiation that would be executed after STARTTLS finished with the client.
- Disconnection log messages are now more standardized across services. They also always now start with "Disconnected" prefix.
- Dovecot now depends on libsystemd for systemd integration.
- Removed support for Lua 5.2. Use version 5.1 or 5.3 instead.
- config: Some settings are now marked as "hidden". It's discouraged to change these settings. They will no longer be visible in doveconf output, except if they have been changed or if doveconf -s parameter is used. See https://doc.dovecot.org/settings/advanced/ for details.
- imap-compress: Compression level is now algorithm specific. See https://doc.dovecot.org/settings/plugin/compress-plugin/
- indexer-worker: Convert "Indexed" info logs to an event named "indexer_worker_indexing_finished". See https://doc.dovecot.org/admin_manual/list_of_events/#indexer-worker-indexing...
- Add TSLv1.3 support to min_protocols.
- Allow configuring ssl_cipher_suites. (for TLSv1.3+)
- acl: Add acl_ignore_namespace setting which allows to entirely ignore ACLs for the listed namespaces.
- imap: Support official RFC8970 preview/snippet syntax. Old methods of retrieving preview information via IMAP commands ("SNIPPET and PREVIEW with explicit algorithm selection") have been deprecated.
- imapc: Support INDEXPVT for imapc storage to enable private message flags for cluster wide shared mailboxes.
- lib-storage: Add new events: mail_opened, mail_expunge_requested, mail_expunged, mail_cache_lookup_finished. See https://doc.dovecot.org/admin_manual/list_of_events/#mail
- zlib, imap-compression, fs-compress: Support compression levels that the algorithm supports. Before, we would allow hardcoded value between 1 to 9 and would default to 6. Now we allow using per-algorithm value range and default to whatever default the algorithm specifies.
- *-login: Commands pipelined together with and just after the authenticate command cause these commands to be executed twice. This applies to all protocols that involve user login, which currently comprises of imap, pop3, submisision and managesieve.
- *-login: Processes are supposed to disconnect the oldest non-logged in connection when process_limit was reached. This didn't actually happen with the default "high-security mode" (with service_count=1) where each connection is handled by a separate process.
- *-login: When login process reaches client/process limits, oldest client connections are disconnected. If one of these was still doing anvil lookup, this caused a crash. This could happen only if the login process limits were very low or if the server was overloaded.
- Fixed building with link time optimizations (-flto).
- auth: Userdb iteration with passwd driver does not always return all users with some nss drivers.
- dsync: Shared INBOX not synced when "mail_shared_explicit_inbox" was disabled. If a user has a shared mailbox which is another user's INBOX, dsync didn't include the mailbox in syncing unless explicit naming is enabled with "mail_shared_explicit_inbox" set to "yes".
- dsync: Shared namespaces were not synced with "-n" flag.
- dsync: Syncing shared INBOX failed if mail_attribute_dict was not set. If a user has a shared mailbox that is another user's INBOX, dsync failed to export the mailbox if mail attributes are disabled.
- fts-solr, fts-tika: Using both Solr FTS and Tika may have caused HTTP requests to assert-crash: Panic: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL)
- fts-tika: 5xx errors returned by Tika server as indexing failures. However, Tika can return 5xx for some attachments every time. So the 5xx error should be retried once, but treated as success if it happens on the retry as well. v2.3 regression.
- fts-tika: v2.3.11 regression: Indexing messages with fts-tika may have resulted in Panic: file message-parser.c: line 802 (message_parser_deinit_from_parts): assertion failed: (ctx->nested_parts_count == 0 || i_stream_have_bytes_left(ctx->input))
- imap: SETMETADATA could not be used to unset metadata values. Instead NIL was handled as a "NIL" string. v2.3.14 regression.
- imap: IMAP BINARY FETCH crashes at least on empty base64 body: Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 || block_idx+1 == block_count)
- imap: If IMAP client using the NOTIFY command was disconnected while sending FETCH notifications to the client, imap could crash with Panic: Trying to close mailbox INBOX with open transactions.
- imap: Using IMAP COMPRESS extension can cause IMAP connection to hang when IMAP commands are >8 kB long.
- imapc: If remote server sent BYE but didn't immediately disconnect, it could cause infinite busy-loop.
- lib-index: Corrupted cache record size in dovecot.index.cache file could have caused a crash (segfault) when accessing it.
- lib-oauth2: JWT token time validation now works correctly with 32-bit systems.
- lib-ssl-iostream: Checking hostnames against an SSL certificate was case-sensitive.
- lib-storage: Corrupted mime.parts in dovecot.index.cache may have resulted in Panic: file imap-bodystructure.c: line 206 (part_write_body): assertion failed: (text == ((part->flags & MESSAGE_PART_FLAG_TEXT) != 0))
- lib-storage: Index rebuilding (e.g. via doveadm force-resync) didn't preserve the "hdr-pop3-uidl" header. Because of this, the next pop3 session could have accessed all of the emails' metadata to read their POP3 UIDL (opening dbox files).
- listescape: When using the listescape plugin and a shared namespace the plugin didn't work properly anymore resulting in errors like: "Invalid mailbox name: Name must not have '/' character."
- lmtp: Connection crashes if connection gets disconnected due to multiple bad commands and the last bad command is BDAT.
- lmtp: The Dovecot-specific LMTP parameter XRCPTFORWARD was blindly forwarded by LMTP proxy without checking that the backend has support. This caused a command parameter error from the backend if it was running an older Dovecot release. This could only occur in more complex setups where the message was proxied twice; when the proxy generated the XRCPTFORWARD parameter itself the problem did not occur, so this only happened when it was forwarded.
- lmtp: The LMTP proxy crashes with a panic when the remote server replies with an error while the mail is still being forwarded through a DATA/BDAT command.
- lmtp: Username may have been missing from lmtp log line prefixes when it was performing autoexpunging.
- master: Dovecot would incorrectly fail with haproxy 2.0.14 service checks.
- master: Systemd service: Dovecot announces readiness for accepting connections earlier than it should. The following environment variables are now imported automatically and can be omitted from import_environment setting: NOTIFY_SOCKET LISTEN_FDS LISTEN_PID.
- master: service { process_min_avail } was launching processes too slowly when master was forking a lot of processes.
- util: Make the health-check.sh example script POSIX shell compatible.
I know I'm blonde so might be silly question, but this libsystemd dependency, does this mean dovecot need it mandatory even if we do not use a systemd infected OS ? Or is it only needed if we use one of those systemd infected OS's?
My question is because our linux does not use systemd Thanks
On Mon, Jun 21, 2021 at 9:19 PM Timo Sirainen <timo@sirainen.com> wrote:
Hi,
Here's a new release with some security fixes and quite a lot of other changes as well.
https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz.sig
Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot
- CVE-2021-29157: Dovecot does not correctly escape kid and azp fields in JWT tokens. This may be used to supply attacker controlled keys to validate tokens, if attacker has local access.
- CVE-2021-33515: On-path attacker could have injected plaintext commands before STARTTLS negotiation that would be executed after STARTTLS finished with the client.
- Disconnection log messages are now more standardized across services. They also always now start with "Disconnected" prefix.
- Dovecot now depends on libsystemd for systemd integration.
- Removed support for Lua 5.2. Use version 5.1 or 5.3 instead.
- config: Some settings are now marked as "hidden". It's discouraged to change these settings. They will no longer be visible in doveconf output, except if they have been changed or if doveconf -s parameter is used. See https://doc.dovecot.org/settings/advanced/ for details.
- imap-compress: Compression level is now algorithm specific. See https://doc.dovecot.org/settings/plugin/compress-plugin/
- indexer-worker: Convert "Indexed" info logs to an event named "indexer_worker_indexing_finished". See
https://doc.dovecot.org/admin_manual/list_of_events/#indexer-worker-indexing...
- Add TSLv1.3 support to min_protocols.
- Allow configuring ssl_cipher_suites. (for TLSv1.3+)
- acl: Add acl_ignore_namespace setting which allows to entirely ignore ACLs for the listed namespaces.
- imap: Support official RFC8970 preview/snippet syntax. Old methods of retrieving preview information via IMAP commands ("SNIPPET and PREVIEW with explicit algorithm selection") have been deprecated.
- imapc: Support INDEXPVT for imapc storage to enable private message flags for cluster wide shared mailboxes.
- lib-storage: Add new events: mail_opened, mail_expunge_requested, mail_expunged, mail_cache_lookup_finished. See https://doc.dovecot.org/admin_manual/list_of_events/#mail
- zlib, imap-compression, fs-compress: Support compression levels that the algorithm supports. Before, we would allow hardcoded value between 1 to 9 and would default to 6. Now we allow using per-algorithm value range and default to whatever default the algorithm specifies.
- *-login: Commands pipelined together with and just after the authenticate command cause these commands to be executed twice. This applies to all protocols that involve user login, which currently comprises of imap, pop3, submisision and managesieve.
- *-login: Processes are supposed to disconnect the oldest non-logged in connection when process_limit was reached. This didn't actually happen with the default "high-security mode" (with service_count=1) where each connection is handled by a separate process.
- *-login: When login process reaches client/process limits, oldest client connections are disconnected. If one of these was still doing anvil lookup, this caused a crash. This could happen only if the login process limits were very low or if the server was overloaded.
- Fixed building with link time optimizations (-flto).
- auth: Userdb iteration with passwd driver does not always return all users with some nss drivers.
- dsync: Shared INBOX not synced when "mail_shared_explicit_inbox" was disabled. If a user has a shared mailbox which is another user's INBOX, dsync didn't include the mailbox in syncing unless explicit naming is enabled with "mail_shared_explicit_inbox" set to "yes".
- dsync: Shared namespaces were not synced with "-n" flag.
- dsync: Syncing shared INBOX failed if mail_attribute_dict was not set. If a user has a shared mailbox that is another user's INBOX, dsync failed to export the mailbox if mail attributes are disabled.
- fts-solr, fts-tika: Using both Solr FTS and Tika may have caused HTTP requests to assert-crash: Panic: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL)
- fts-tika: 5xx errors returned by Tika server as indexing failures. However, Tika can return 5xx for some attachments every time. So the 5xx error should be retried once, but treated as success if it happens on the retry as well. v2.3 regression.
- fts-tika: v2.3.11 regression: Indexing messages with fts-tika may have resulted in Panic: file message-parser.c: line 802 (message_parser_deinit_from_parts): assertion failed: (ctx->nested_parts_count == 0 || i_stream_have_bytes_left(ctx->input))
- imap: SETMETADATA could not be used to unset metadata values. Instead NIL was handled as a "NIL" string. v2.3.14 regression.
- imap: IMAP BINARY FETCH crashes at least on empty base64 body: Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 || block_idx+1 == block_count)
- imap: If IMAP client using the NOTIFY command was disconnected while sending FETCH notifications to the client, imap could crash with Panic: Trying to close mailbox INBOX with open transactions.
- imap: Using IMAP COMPRESS extension can cause IMAP connection to hang when IMAP commands are >8 kB long.
- imapc: If remote server sent BYE but didn't immediately disconnect, it could cause infinite busy-loop.
- lib-index: Corrupted cache record size in dovecot.index.cache file could have caused a crash (segfault) when accessing it.
- lib-oauth2: JWT token time validation now works correctly with 32-bit systems.
- lib-ssl-iostream: Checking hostnames against an SSL certificate was case-sensitive.
- lib-storage: Corrupted mime.parts in dovecot.index.cache may have resulted in Panic: file imap-bodystructure.c: line 206 (part_write_body): assertion failed: (text == ((part->flags & MESSAGE_PART_FLAG_TEXT) != 0))
- lib-storage: Index rebuilding (e.g. via doveadm force-resync) didn't preserve the "hdr-pop3-uidl" header. Because of this, the next pop3 session could have accessed all of the emails' metadata to read their POP3 UIDL (opening dbox files).
- listescape: When using the listescape plugin and a shared namespace the plugin didn't work properly anymore resulting in errors like: "Invalid mailbox name: Name must not have '/' character."
- lmtp: Connection crashes if connection gets disconnected due to multiple bad commands and the last bad command is BDAT.
- lmtp: The Dovecot-specific LMTP parameter XRCPTFORWARD was blindly forwarded by LMTP proxy without checking that the backend has support. This caused a command parameter error from the backend if it was running an older Dovecot release. This could only occur in more complex setups where the message was proxied twice; when the proxy generated the XRCPTFORWARD parameter itself the problem did not occur, so this only happened when it was forwarded.
- lmtp: The LMTP proxy crashes with a panic when the remote server replies with an error while the mail is still being forwarded through a DATA/BDAT command.
- lmtp: Username may have been missing from lmtp log line prefixes when it was performing autoexpunging.
- master: Dovecot would incorrectly fail with haproxy 2.0.14 service checks.
- master: Systemd service: Dovecot announces readiness for accepting connections earlier than it should. The following environment variables are now imported automatically and can be omitted from import_environment setting: NOTIFY_SOCKET LISTEN_FDS LISTEN_PID.
- master: service { process_min_avail } was launching processes too slowly when master was forking a lot of processes.
- util: Make the health-check.sh example script POSIX shell compatible.
Hi,
On 21. Jun 2021, at 15.19, Laura Steynes <laura.steynes72@gmail.com> wrote:
I know I'm blonde so might be silly question, but this libsystemd dependency, does this mean dovecot need it mandatory even if we do not use a systemd infected OS ? Or is it only needed if we use one of those systemd infected OS's?
My question is because our linux does not use systemd
No, systemd isn't required. It's just that previously when Dovecot was compiled with systemd it used our built-in copy of some of the systemd code, while now it links to libsystemd. Even if Dovecot is compiled against libsystemd it doesn't require actually to use it.
the github release is still missing, true?
git remote add -t release-2.3.15 origin https://github.com/dovecot/core <https://github.com/dovecot/core> #6 21.37 + git fetch '--depth=1' #6 21.81 fatal: couldn't find remote ref refs/heads/release-2.3.15
Yeah, sorry, it took a while to push to github. It had been a long time since I last finished the release myself, so I was fighting with gpg signing the release tags before pushing to github. It had such helpful error messages like "gpg failed to sign the data", "signing failed: Invalid IPC response" and finally I got to "signing failed: No secret key" (pretty sure there was) after which I gave up and signed elsewhere.
Il 21/06/21 13:18, Timo Sirainen ha scritto:
+ imap: Support official RFC8970 preview/snippet syntax. Old methods of retrieving preview information via IMAP commands ("SNIPPET and PREVIEW with explicit algorithm selection") have been deprecated.
Hi,
After upgrading dovecot from 2.3.14 to 2.3.15 I noticed a problem parsing FETCH response of PREVIEW attribute.
Basically there is any space after the preview content and the rest of the string which causes issues on parsing:
a UID FETCH 2539 (MODSEQ UID FLAGS INTERNALDATE PREVIEW BODY.PEEK[HEADER.FIELDS (FROM TO SUBJECT DATE)])
- 8 FETCH (UID 2539 MODSEQ (3) FLAGS (\Seen $HasNoAttachment) INTERNALDATE "04-Mar-2021 12:18:02 +0100" PREVIEW "test"BODY[HEADER.FIELDS (FROM TO SUBJECT DATE)] {151}
With dovecot 2.3.14 there was no problem:
a UID FETCH 2539 (MODSEQ UID FLAGS INTERNALDATE PREVIEW BODY.PEEK[HEADER.FIELDS (FROM TO SUBJECT DATE)])
- 8 FETCH (UID 2539 MODSEQ (3) FLAGS (\Seen $HasNoAttachment) INTERNALDATE "04-Mar-2021 12:18:02 +0100" PREVIEW (FUZZY "test") BODY[HEADER.FIELDS (FROM TO SUBJECT DATE)] {151}
Can you check it please? Thanks
-- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice
On 06/22/2021 10:50 AM Alessio Cecchi <alessio@skye.it> wrote:
Il 21/06/21 13:18, Timo Sirainen ha scritto:
+ imap: Support official RFC8970 preview/snippet syntax. Old methods of retrieving preview information via IMAP commands ("SNIPPET and PREVIEW with explicit algorithm selection") have been deprecated.
Hi,
After upgrading dovecot from 2.3.14 to 2.3.15 I noticed a problem parsing FETCH response of PREVIEW attribute.
Basically there is any space after the preview content and the rest of the string which causes issues on parsing:
a UID FETCH 2539 (MODSEQ UID FLAGS INTERNALDATE PREVIEW BODY.PEEK[HEADER.FIELDS (FROM TO SUBJECT DATE)]) * 8 FETCH (UID 2539 MODSEQ (3) FLAGS (\Seen $HasNoAttachment) INTERNALDATE "04-Mar-2021 12:18:02 +0100" PREVIEW "test"BODY[HEADER.FIELDS (FROM TO SUBJECT DATE)] {151}
With dovecot 2.3.14 there was no problem:
a UID FETCH 2539 (MODSEQ UID FLAGS INTERNALDATE PREVIEW BODY.PEEK[HEADER.FIELDS (FROM TO SUBJECT DATE)]) * 8 FETCH (UID 2539 MODSEQ (3) FLAGS (\Seen $HasNoAttachment) INTERNALDATE "04-Mar-2021 12:18:02 +0100" PREVIEW (FUZZY "test") BODY[HEADER.FIELDS (FROM TO SUBJECT DATE)] {151}
Yes, this is an unfortunate regression if PREVIEW is not the last FETCH option listed in the command. Fix is: diff --git a/src/imap/imap-fetch-body.c b/src/imap/imap-fetch-body.c index 59a9b24d99..39e66f093d 100644 --- a/src/imap/imap-fetch-body.c +++ b/src/imap/imap-fetch-body.c @@ -648,6 +648,7 @@ fetch_snippet(struct imap_fetch_context *ctx, struct mail *mail, str_append(ctx->state.cur_str, "NIL"); if (preview->old_standard) str_append(ctx->state.cur_str, ")"); + str_append_c(ctx->state.cur_str, ' '); return 1; } michael
participants (4)
-
Alessio Cecchi
-
Laura Steynes
-
Michael Slusarz
-
Timo Sirainen