CVE-2021-32055: Critical severity Mutt Mutt vulnerability
Last updated 16 January 2025
Other sources
Mutt 1.11.0 through 2.0.x before 2.0.7 (and NeoMutt 2019-10-25 through 2021-05-04) has a $imapqresync 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 $imapqresync setting for QRESYNC is not enabled by default.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/muttto a version that resolves this vulnerability.Fixed in 2.0.5-4.1+deb11u3Fixed in 2.2.12-0.1~deb12u1Fixed in 2.2.9-1+deb12u1Fixed in 2.2.13-1 - Upgrade
Upgrade
debian/neomuttto a version that resolves this vulnerability.Fixed in 20201127+dfsg.1-1.2Fixed in 20220429+dfsg1-4.1Fixed in 20250404+dfsg-2 - Upgrade
Upgrade
alpine/neomuttto a version that resolves this vulnerability.Fixed in 20211015-r0 - Upgrade
Upgrade
Muttto a version that resolves this vulnerability.Fixed in 2.0.7
Event History
Frequently Asked Questions
What is CVE-2021-32055?
CVE-2021-32055 is a vulnerability in Mutt and NeoMutt which allows for an out-of-bounds read due to a $imap_qresync issue.
How severe is CVE-2021-32055?
CVE-2021-32055 has a severity value of 9.1, which is considered critical.
Which software versions are affected by CVE-2021-32055?
Mutt versions 1.11.0 through 2.0.x (before 2.0.7) and NeoMutt versions 2019-10-25 through 2021-05-04 are affected by CVE-2021-32055.
How can I fix CVE-2021-32055?
To fix CVE-2021-32055, upgrade to Mutt version 2.0.7 or later, or upgrade to a later version of NeoMutt after 2021-05-04.
Where can I find more information about CVE-2021-32055?
For more information about CVE-2021-32055, you can refer to the following references: [Link 1](http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20210503/000036.html), [Link 2](https://github.com/neomutt/neomutt/commit/fa1db5785e5cfd9d3cd27b7571b9fe268d2ec2dc), [Link 3](https://gitlab.com/muttmua/mutt/-/commit/7c4779ac24d2fb68a2a47b58c7904118f40965d5).