CVE-2024-49394

NameCVE-2024-49394
DescriptionIn 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.
SourceCVE (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 PackageReleaseVersionStatus
mutt (PTS)bullseye (security), bullseye2.0.5-4.1+deb11u3vulnerable
bookworm2.2.12-0.1~deb12u1vulnerable
bookworm (security)2.2.9-1+deb12u1vulnerable
sid, trixie2.2.13-1vulnerable
neomutt (PTS)bullseye20201127+dfsg.1-1.2vulnerable
bookworm20220429+dfsg1-4.1vulnerable
trixie20241114+dfsg1-1fixed
sid20241212+dfsg-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
muttsource(unstable)(unfixed)unimportant
neomuttsource(unstable)20241002+dfsg-1unimportant

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
Protected headers introduced in mutt 1.12

Search for package or bug name: Reporting problems