Show filters
21 Total Results
Displaying 1-10 of 21
Sort by:
Attacker Value
Unknown
CVE-2024-49395
Disclosure Date: November 12, 2024 (last updated November 15, 2024)
In mutt and neomutt, PGP encryption does not use the --hidden-recipient mode which may leak the Bcc email header field by inferring from the recipients info.
0
Attacker Value
Unknown
CVE-2024-49394
Disclosure Date: November 12, 2024 (last updated November 15, 2024)
In mutt and neomutt the In-Reply-To email header field is not protected by cryptographic signing which allows an attacker to reuse an unencrypted but signed email message to impersonate the original sender.
0
Attacker Value
Unknown
CVE-2024-49393
Disclosure Date: November 12, 2024 (last updated November 15, 2024)
In neomutt and mutt, the To and Cc email headers are not validated by cryptographic signing which allows an attacker that intercepts a message to change their value and include himself as a one of the recipients to compromise message confidentiality.
0
Attacker Value
Unknown
CVE-2021-32055
Disclosure Date: May 05, 2021 (last updated November 28, 2024)
Mutt 1.11.0 through 2.0.x before 2.0.7 (and NeoMutt 2019-10-25 through 2021-05-04) has a $imap_qresync issue in which imap/util.c has an out-of-bounds read in situations where an IMAP sequence set ends with a comma. NOTE: the $imap_qresync setting for QRESYNC is not enabled by default.
0
Attacker Value
Unknown
CVE-2020-28896
Disclosure Date: November 23, 2020 (last updated November 28, 2024)
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.
0
Attacker Value
Unknown
CVE-2020-14954
Disclosure Date: June 21, 2020 (last updated November 08, 2023)
Mutt before 1.14.4 and NeoMutt before 2020-06-19 have a STARTTLS buffering issue that affects IMAP, SMTP, and POP3. When a server sends a "begin TLS" response, the client reads additional data (e.g., from a man-in-the-middle attacker) and evaluates it in a TLS context, aka "response injection."
0
Attacker Value
Unknown
CVE-2018-14351
Disclosure Date: July 17, 2018 (last updated November 27, 2024)
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size.
0
Attacker Value
Unknown
CVE-2018-14349
Disclosure Date: July 17, 2018 (last updated November 27, 2024)
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a NO response without a message.
0
Attacker Value
Unknown
CVE-2018-14352
Disclosure Date: July 17, 2018 (last updated November 27, 2024)
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap_quote_string in imap/util.c does not leave room for quote characters, leading to a stack-based buffer overflow.
0
Attacker Value
Unknown
CVE-2018-14354
Disclosure Date: July 17, 2018 (last updated November 27, 2024)
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They allow remote IMAP servers to execute arbitrary commands via backquote characters, related to the mailboxes command associated with a manual subscription or unsubscription.
0