Mutt before 2.0.2 and NeoMutt before 2020-11-20 did not ensure that $ssl_force_tls was processed if an IMAP server's initial server response was invalid. The connection was not properly closed, and the code could continue attempting to authenticate. This could result in authentication credentials being exposed on an unencrypted connection, or to a machine-in-the-middle.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
| Link | Tags |
|---|---|
| https://gitlab.com/muttmua/mutt/-/commit/d92689088dfe80a290ec836e292376e2d9984f8f | third party advisory patch |
| https://gitlab.com/muttmua/mutt/-/commit/04b06aaa3e0cc0022b9b01dbca2863756ebbf59a | third party advisory patch |
| https://github.com/neomutt/neomutt/commit/9c36717a3e2af1f2c1b7242035455ec8112b4b06 | third party advisory patch |
| https://github.com/neomutt/neomutt/releases/tag/20201120 | third party advisory release notes |
| https://lists.debian.org/debian-lts-announce/2020/11/msg00048.html | third party advisory mailing list |
| https://security.gentoo.org/glsa/202101-32 | third party advisory vendor advisory |