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.
References
Link | Resource |
---|---|
https://github.com/neomutt/neomutt/commit/9c36717a3e2af1f2c1b7242035455ec8112b4b06 | Patch Third Party Advisory |
https://github.com/neomutt/neomutt/releases/tag/20201120 | Release Notes Third Party Advisory |
https://gitlab.com/muttmua/mutt/-/commit/04b06aaa3e0cc0022b9b01dbca2863756ebbf59a | Patch Third Party Advisory |
https://gitlab.com/muttmua/mutt/-/commit/d92689088dfe80a290ec836e292376e2d9984f8f | Patch Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/11/msg00048.html | Mailing List Third Party Advisory |
https://security.gentoo.org/glsa/202101-32 | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2020-11-23 19:15
Updated : 2024-02-28 18:08
NVD link : CVE-2020-28896
Mitre link : CVE-2020-28896
CVE.ORG link : CVE-2020-28896
JSON object : View
Products Affected
debian
- debian_linux
mutt
- mutt
neomutt
- neomutt