| Name | CVE-2024-49394 |
| Description | 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| mutt (PTS) | jessie, jessie (lts) | 1.5.23-3+deb8u7 | vulnerable |
| stretch (security) | 1.7.2-1+deb9u6 | vulnerable |
| stretch (lts), stretch | 1.7.2-1+deb9u7 | vulnerable |
| buster (security), buster, buster (lts) | 1.10.1-2.1+deb10u7 | vulnerable |
| bullseye (security), bullseye | 2.0.5-4.1+deb11u3 | vulnerable |
| bookworm | 2.2.12-0.1~deb12u1 | vulnerable |
| bookworm (security) | 2.2.9-1+deb12u1 | vulnerable |
| sid, trixie | 2.2.13-1 | vulnerable |
| neomutt (PTS) | buster | 20180716+dfsg.1-1+deb10u2 | vulnerable |
| buster (security), buster (lts) | 20180716+dfsg.1-1+deb10u1 | vulnerable |
| bullseye | 20201127+dfsg.1-1.2 | vulnerable |
| bookworm | 20220429+dfsg1-4.1 | vulnerable |
| sid, trixie | 20241114+dfsg-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| mutt | source | (unstable) | (unfixed) | unimportant | | |
| neomutt | source | buster | (unfixed) | end-of-life | | |
| neomutt | source | (unstable) | 20241002+dfsg-1 | unimportant | | |
Notes
https://bugzilla.redhat.com/show_bug.cgi?id=2325330
https://gitlab.com/muttmua/mutt/-/issues/490
Mutt project does not plan to address CVE-2024-49393, CVE-2024-49394, CVE-2024-49395
cf. https://gitlab.com/muttmua/mutt/-/issues/490#note_2209448655 . Issues with documented
through http://mutt.org/doc/manual/#crypt-protected-headers-read
https://github.com/neomutt/neomutt/issues/4226
Protected since: https://github.com/neomutt/neomutt/commit/13cfc6f98322eafdc30ecc4c15999d401950a1d9 (20241002)
Reading protected value since: https://github.com/neomutt/neomutt/commit/ec02b141983c70ae7ebee0cdfba59e90a825f0cc (20241002)
These are longstanding limitations of PGP-encrypted mail and rather enhancements
than actual vulnerabilities
[buster] - mutt <ignored> (Minor issue; upstream won't fix; protected headers introduced in 1.12)
[stretch] - mutt <ignored> (Minor issue; upstream won't fix; protected headers introduced in 1.12)
[jessie] - mutt <ignored> (Minor issue; upstream won't fix; protected headers introduced in 1.12)