LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Mutt and NeoMutt may treat a signed email as trustworthy while an important threading header, In-Reply-To, is not covered by the signature. An attacker could reuse a signed, unencrypted message in a different reply context to appear as the original sender. Business impact is mainly trust and integrity risk in email-driven decisions.

Executive priority

Treat as a targeted integrity risk, not an emergency outage issue. Prioritize if signed email is used for approvals, legal, finance, engineering releases, or executive communications. Patch through normal vendor channels once available.

Technical view

CVE-2024-49394 is a CWE-347 cryptographic verification weakness. The In-Reply-To header is not protected by signing in mutt/neomutt, enabling replay or contextual misuse of a signed unencrypted message. CVSS 3.1 is 5.3, with network attack vector, low complexity, no privileges, and low integrity impact.

Likely exposure

Environments using mutt or NeoMutt for signed email handling are most relevant. Red Hat lists RHEL 8 and RHEL 9 mutt as affected, RHEL 7 as unknown. The source bundle does not provide exact affected version ranges.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The likely abuse case is social or process manipulation: making a legitimate signed message appear related to a different email thread or decision context.

Researcher notes

Evidence is incomplete on exact vulnerable versions and final fixed releases in the provided bundle. Upstream NeoMutt issue and pull-request links indicate active project handling, but remediation details should be verified directly from those sources and vendor advisories.

Mitigation direction

  • Check Red Hat and upstream NeoMutt guidance for fixed packages or configuration advice.
  • Prioritize review of RHEL 8 and RHEL 9 systems with mutt installed.
  • Update mutt/neomutt when vendor-supported fixes are available.
  • Do not rely on thread context alone to validate signed email intent.
  • Educate sensitive workflow owners about signed-message replay context risk.

Validation and detection

  • Inventory systems with mutt or NeoMutt installed.
  • Compare installed packages against vendor advisories for CVE-2024-49394.
  • Confirm RHEL 8 and RHEL 9 exposure where mutt is present.
  • Track the linked Red Hat Bugzilla and NeoMutt GitHub issue or pull requests.
  • Review processes where signed emails authorize payments, approvals, or account changes.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-347: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-49394 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4redhat

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2024-49394Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineredhat

    Reported to Red Hat.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendormuttmuttaffected
Red HatRed Hat Enterprise Linux 7muttunknown
Red HatRed Hat Enterprise Linux 8muttaffected
Red HatRed Hat Enterprise Linux 9muttaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.