CVE Tools

CVE-2024-49394

Mutt: neomutt: in-reply-to email header field it not protected by cryptograpic signing

Published: Nov 12, 2024Updated: Nov 14, 2024 Sources: CVE List NVDCWE-347
5.3CVSSMEDIUM

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.

CVSS Vector Breakdown

AV:NAC:LPR:NUI:NS:UC:NI:LA:N
Exploitability
AV:NAttack Vector
Network
AC:LAttack Complexity
Low
PR:NPrivileges Required
None
UI:NUser Interaction
None
Scope
S:UScope
Unchanged
Impact
C:NConfidentiality
None
I:LIntegrity
Low
A:NAvailability
None

Weaknesses

Affected Products

muttoss-projectUSCommunicationsaka mutt mail client
redhatcommercialUSOperating Systemsaka red hat
red hatcommercialUSOperating Systemsaka red hat
and 2 more affected products View all →

Attack Graph

Products CVE Techniques Tactics

Click technique nodes to view MITRE ATT&CK details. Scroll to zoom, drag to pan.

Exploitability

No known exploits, KEV entries, or remediation guidance available for this vulnerability yet.

MITRE ATT&CK

1 technique
Collection
View detailed technique mapping

References

Timeline

Published
Nov 12, 2024
Last Updated
Nov 14, 2024

Unlock Complete Vulnerability Intelligence

Get the full picture for CVE-2024-49394 and every CVE in our database. Create a free account — no credit card required.

Create Free Account
Plain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows