Bugs fixes in "mutt"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2021-3181 | rfc822.c in Mutt through 2.0.4 allows remote attackers to cause a denial of service (mailbox unavailability) by sending email messages with sequences | 2021-01-25 |
| CVE | CVE-2021-3181 | rfc822.c in Mutt through 2.0.4 allows remote attackers to cause a denial of service (mailbox unavailability) by sending email messages with sequences | 2021-01-25 |
| CVE | CVE-2021-3181 | rfc822.c in Mutt through 2.0.4 allows remote attackers to cause a denial of service (mailbox unavailability) by sending email messages with sequences | 2021-01-25 |
| CVE | CVE-2021-3181 | rfc822.c in Mutt through 2.0.4 allows remote attackers to cause a denial of service (mailbox unavailability) by sending email messages with sequences | 2021-01-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-28896 | 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 inva | 2020-11-25 |
| CVE | CVE-2020-14954 | 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" | 2020-06-24 |
| Launchpad | 1884588 | Certificate problems sending mail | 2020-06-24 |
| CVE | CVE-2020-14954 | 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" | 2020-06-24 |
| Launchpad | 1884588 | Certificate problems sending mail | 2020-06-24 |
| CVE | CVE-2020-14954 | 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" | 2020-06-24 |
| Launchpad | 1884588 | Certificate problems sending mail | 2020-06-24 |
| CVE | CVE-2020-14954 | 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" | 2020-06-24 |
| CVE | CVE-2020-14954 | 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" | 2020-06-24 |
About
-
Send Feedback to @ubuntu_updates
