rpm package
opensuse/neomutt&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/neomutt&distro=openSUSE%20Tumbleweed
Vulnerabilities (23)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-49394 | Med | 5.3 | < 20241114-1.1 | 20241114-1.1 | Nov 12, 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. | |
| CVE-2024-49393 | Med | 6.5 | < 20241114-1.1 | 20241114-1.1 | Nov 12, 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. | |
| CVE-2022-1328 | Med | 4.3 | < 20220429-1.1 | 20220429-1.1 | Apr 14, 2022 | Buffer Overflow in uudecoder in Mutt affecting all versions starting from 0.94.13 before 2.2.3 allows read past end of input line | |
| CVE-2021-32055 | Cri | 9.1 | < 20211029-1.1 | 20211029-1.1 | May 5, 2021 | 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 de | |
| CVE-2020-28896 | Med | 5.3 | < 20210205-3.3 | 20210205-3.3 | Nov 23, 2020 | 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 authentic | |
| CVE-2020-14954 | Med | 5.9 | < 20210205-3.3 | 20210205-3.3 | Jun 21, 2020 | 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 "respo | |
| CVE-2020-14154 | Med | 4.8 | < 20210205-3.3 | 20210205-3.3 | Jun 15, 2020 | Mutt before 1.14.3 proceeds with a connection even if, in response to a GnuTLS certificate prompt, the user rejects an expired intermediate certificate. | |
| CVE-2020-14093 | Med | 5.9 | < 20210205-3.3 | 20210205-3.3 | Jun 15, 2020 | Mutt before 1.14.3 allows an IMAP fcc/postpone man-in-the-middle attack via a PREAUTH response. | |
| CVE-2018-14363 | Hig | 7.5 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames. | |
| CVE-2018-14362 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c does not forbid characters that may have unsafe interaction with message-cache pathnames, as demonstrated by a '/' character. | |
| CVE-2018-14361 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in NeoMutt before 2018-07-16. nntp.c proceeds even if memory allocation fails for messages data. | |
| CVE-2018-14360 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in NeoMutt before 2018-07-16. nntp_add_group in newsrc.c has a stack-based buffer overflow because of incorrect sscanf usage. | |
| CVE-2018-14359 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They have a buffer overflow via base64 data. | |
| CVE-2018-14358 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long RFC822.SIZE field. | |
| CVE-2018-14357 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | 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 an automatic subscription. | |
| CVE-2018-14356 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c mishandles a zero-length UID. | |
| CVE-2018-14355 | Med | 5.3 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/util.c mishandles ".." directory traversal in a mailbox name. | |
| CVE-2018-14354 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | 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. | |
| CVE-2018-14353 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap_quote_string in imap/util.c has an integer underflow. | |
| CVE-2018-14352 | Cri | 9.8 | < 20210205-3.3 | 20210205-3.3 | Jul 17, 2018 | 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. |
- affected < 20241114-1.1fixed 20241114-1.1
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.
- affected < 20241114-1.1fixed 20241114-1.1
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.
- affected < 20220429-1.1fixed 20220429-1.1
Buffer Overflow in uudecoder in Mutt affecting all versions starting from 0.94.13 before 2.2.3 allows read past end of input line
- affected < 20211029-1.1fixed 20211029-1.1
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 de
- affected < 20210205-3.3fixed 20210205-3.3
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 authentic
- affected < 20210205-3.3fixed 20210205-3.3
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 "respo
- affected < 20210205-3.3fixed 20210205-3.3
Mutt before 1.14.3 proceeds with a connection even if, in response to a GnuTLS certificate prompt, the user rejects an expired intermediate certificate.
- affected < 20210205-3.3fixed 20210205-3.3
Mutt before 1.14.3 allows an IMAP fcc/postpone man-in-the-middle attack via a PREAUTH response.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c does not forbid characters that may have unsafe interaction with message-cache pathnames, as demonstrated by a '/' character.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in NeoMutt before 2018-07-16. nntp.c proceeds even if memory allocation fails for messages data.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in NeoMutt before 2018-07-16. nntp_add_group in newsrc.c has a stack-based buffer overflow because of incorrect sscanf usage.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They have a buffer overflow via base64 data.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long RFC822.SIZE field.
- affected < 20210205-3.3fixed 20210205-3.3
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 an automatic subscription.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c mishandles a zero-length UID.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/util.c mishandles ".." directory traversal in a mailbox name.
- affected < 20210205-3.3fixed 20210205-3.3
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.
- affected < 20210205-3.3fixed 20210205-3.3
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap_quote_string in imap/util.c has an integer underflow.
- affected < 20210205-3.3fixed 20210205-3.3
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.
Page 1 of 2