Package: mutt / 1.7.2-1+deb9u3
Metadata
| Package | Version | Patches format |
|---|---|---|
| mutt | 1.7.2-1+deb9u3 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| neomutt 20170113.patch | (download) |
ChangeLog.neomutt |
499 499 + 0 - 0 ! |
--- |
| neomutt devel/832971 reset xlabel.patch | (download) |
copy.c |
3 1 + 2 - 0 ! |
--- |
| debian specific/Muttrc.patch | (download) |
doc/Muttrc.head |
39 37 + 2 - 0 ! |
muttrc * 2009-01-15 myon: refreshed for mutt-1.5.19; drop our list of ignored headers in favor of upstream's new unignore list Signed-off-by: Matteo F. Vescovi <mfvescovi@gmail.com> |
| debian specific/Md.etc_mailname_gethostbyname.patch | (download) |
init.c |
32 30 + 2 - 0 ! |
md.etc_mailname_gethostbyname If /etc/mailname is present, the hostname inside the file will be used, rather than calling gethostbyname() on the actual hostname. |
| debian specific/use_usr_bin_editor.patch | (download) |
init.c |
2 1 + 1 - 0 ! |
use_usr_bin_editor Even if EDITOR is not set, mutt will always use /usr/bin/editor (which is set by update-alternatives), rather than falling back to vi. |
| debian specific/correct_docdir_in_man_page.patch | (download) |
doc/mutt.man |
2 1 + 1 - 0 ! |
correct_docdir_in_man_page Fix the link so it points to the correct docdir and gzipped manual. |
| debian specific/dont_document_not_present_features.patch | (download) |
functions.h |
2 1 + 1 - 0 ! |
dont_document_not_present_features As the patch says, this will add an include so only documented options for Debian will be used. |
| debian specific/document_debian_defaults.patch | (download) |
init.h |
19 19 + 0 - 0 ! |
document_debian_defaults Some customization of the option which are straying from the default only on Debian systems. |
| debian specific/467432 write_bcc.patch | (download) |
headers.c |
2 1 + 1 - 0 ! |
467432-write_bcc MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit The purpose of this patch is to alter the behavior of the write_bcc option because exim4, the default SMTP in Debian, does not strip the Bcc headers; by default write_bcc is set so this could cause a privacy leak. The behavior that this patch introduces is: never write the Bcc header when the message is sent, otherwise, if the message is sent to Fcc, then this optin will be evaluated and the Bcc header will be written based on that. Background discussion on this is in the following bugs: http://bugs.debian.org/304718 http://bugs.debian.org/467432 This patch is a slightly modified version of the patch provided by Stefan Vlkel <stefan@bc-bd.org> in the second bug. |
| debian specific/566076 build_doc_adjustments.patch | (download) |
doc/Makefile.am |
8 3 + 5 - 0 ! |
566076-build_doc_adjustments Use w3m to build the txt manual. |
| debian specific/828751 pinentry gpg2 support.patch | (download) |
contrib/gpg.rc |
26 18 + 8 - 0 ! |
--- |
| misc/gpg.rc paths.patch | (download) |
contrib/gpg.rc |
11 2 + 9 - 0 ! |
gpg.rc-paths Use the correct path of pgpewrap. |
| misc/smime.rc.patch | (download) |
contrib/smime.rc |
21 11 + 10 - 0 ! |
smime.rc Add CA's provided by ca-certificates to the ones distributed by the default installation of Mutt. Signed-off-by: Matteo F. Vescovi <mfv@debian.org> |
| upstream/528233 readonly open.patch | (download) |
attach.c |
5 5 + 0 - 0 ! |
528233-readonly-open Open attachments as read-only so the editor won't be able to modify it; otherwise the user can believe that he/she can edit it and risk to lose his/her work (see upstream bug http://bugs.mutt.org/3261) Debian bugs: #528233, updated in #572203 |
| upstream/228671 pipe mime.patch | (download) |
imap/message.c |
12 9 + 3 - 0 ! |
228671-pipe-mime Don't draw imap fetch progress if we aren't in visual mode. Drawing progress leaves terminal in confusing state when piping a message from pager to less(1). See http://bugs.mutt.org/1771 Updated in Debian bug #569279 |
| upstream/383769 score match.patch | (download) |
score.c |
2 1 + 1 - 0 ! |
383769-score-match Better matching for ~f, same as mutt-ng did. (see upstream http://bugs.mutt.org/2179) |
| upstream/771125 CVE 2014 9116 jessie.patch | (download) |
lib.c |
3 3 + 0 - 0 ! |
771125-cve-2014-9116-jessie This patch solves the issue raised by CVE-2014-9116 in bug 771125. We correctly redefine what are the whitespace characters as per RFC5322; by doing so we prevent mutt_substrdup from being used in a way that could lead to a segfault. The lib.c part was written by Antonio Radici <antonio@debian.org> to prevent crashes due to this kind of bugs from happening again. |
| upstream/611410 no implicit_autoview for text html.patch | (download) |
init.h |
4 3 + 1 - 0 ! |
--- |
| upstream/693993 manpage corrections.patch | (download) |
init.h |
3 2 + 1 - 0 ! |
--- |
| upstream/749483 conststrings.patch | (download) |
txt2c.sh |
2 1 + 1 - 0 ! |
--- |
| upstream/644992 ipv6 literal.patch | (download) |
mutt_socket.c |
12 11 + 1 - 0 ! |
--- |
| upstream/904051 CVE 2018 14354 CVE 2018 14357.patch | (download) |
imap/command.c |
5 3 + 2 - 0 ! |
[patch] properly quote imap mailbox names when (un)subscribing. When handling automatic subscription (via $imap_check_subscribed), or manual subscribe/unsubscribe commands, mutt generating a "mailboxes" command but failed to properly escape backquotes. Thanks to Jeriko One for the detailed bug report and patch, which this commit is based upon. |
| upstream/904051 CVE 2018 14352 CVE 2018 14353.patch | (download) |
imap/util.c |
19 14 + 5 - 0 ! |
[patch] fix imap_quote_string() length check errors. The function wasn't properly checking for dlen<2 before quoting, and wasn't properly pre-adjusting dlen to include the initial quote. Thanks to Jeriko One for reporting these issues. |
| upstream/904051 CVE 2018 14356.patch | (download) |
pop.c |
4 4 + 0 - 0 ! |
[patch] ensure uid in fetch_uidl. |
| upstream/904051 CVE 2018 14362.patch | (download) |
pop.c |
31 25 + 6 - 0 ! |
[patch] sanitize pop bcache paths. Protect against bcache directory path traversal for UID values. Thanks for Jeriko One for the bug report and patch, which this commit is based upon. |
| upstream/904051 CVE 2018 14355.patch | (download) |
imap/util.c |
7 7 + 0 - 0 ! |
[patch] selectively cache headers. Thanks to NeoMutt and Jeriko One for the patch, which was slightly modified to apply to the Mutt code. |
| upstream/904051 CVE 2018 14350 CVE 2018 14358.patch | (download) |
imap/message.c |
13 11 + 2 - 0 ! |
[patch] don't overflow tmp in msg_parse_fetch. Ensure INTERNALDATE and RFC822.SIZE field sizes fit temp buffer. Thanks to Jeriko One for the bug report and patch, which this patch is based upon. |
| upstream/904051 CVE 2018 14349.patch | (download) |
imap/command.c |
2 1 + 1 - 0 ! |
[patch] handle no response without message properly |
| upstream/904051 CVE 2018 14351.patch | (download) |
imap/command.c |
7 7 + 0 - 0 ! |
[patch] verify imap status mailbox literal count size. Ensure the length isn't bigger than the idata->buf. Thanks to Jeriko One fo the bug report and patch, which this commit is based upon. |
| upstream/904051 CVE 2018 14359.patch | (download) |
base64.c |
8 7 + 1 - 0 ! |
[patch] check outbuf length in mutt_from_base64() The obuf can be overflowed in auth_cram.c, and possibly auth_gss.c. Thanks to Jeriko One for the bug report. |
| upstream/904051 CVE 2018 14360.patch | (download) |
newsrc.c |
9 6 + 3 - 0 ! |
[patch] set length modifiers for group and desc nntp_add_group parses a line controlled by the connected nntp server. Restrict the maximum lengths read into the stack buffers group, and desc. |
| upstream/904051 CVE 2018 14361.patch | (download) |
nntp.c |
2 2 + 0 - 0 ! |
[patch] add alloc fail check in nntp_fetch_headers |
| upstream/904051 CVE 2018 14363.patch | (download) |
newsrc.c |
13 12 + 1 - 0 ! |
[patch] sanitise cache paths Co-authored-by: JerikoOne <jeriko.one@gmx.us> |
| security/CVE 2020 14093.patch | (download) |
imap/imap.c |
16 16 + 0 - 0 ! |
--- |
| security/CVE not yet released.patch | (download) |
mutt_socket.c |
30 30 + 0 - 0 ! |
[patch] fix starttls response injection attack. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Thanks again to Damian Poddebniak and Fabian Ising from the Mnster University of Applied Sciences for reporting this issue. Their summary in ticket 248 states the issue clearly: We found another STARTTLS-related issue in Mutt. Unfortunately, it affects SMTP, POP3 and IMAP. When the server responds with its "let's do TLS now message", e.g. A OK begin TLS\r\n in IMAP or +OK begin TLS\r\n in POP3, Mutt will also read any data after the \r\n and save it into some internal buffer for later processing. This is problematic, because a MITM attacker can inject arbitrary responses. There is a nice blogpost by Wietse Venema about a "command injection" in postfix (http://www.postfix.org/CVE-2011-0411.html). What we have here is the problem in reverse, i.e. not a command injection, but a "response injection." This commit fixes the issue by clearing the CONNECTION input buffer in mutt_ssl_starttls(). To make backporting this fix easier, the new functions only clear the top-level CONNECTION buffer; they don't handle nested buffering in mutt_zstrm.c or mutt_sasl.c. However both of those wrap the connection *after* STARTTLS, so this is currently okay. mutt_tunnel.c occurs before connecting, but it does not perform any nesting. |
