CVE-2005-2351 json
Mutt before 1.5.20 patch 7 allows an attacker to cause a denial of service via a series of requests to mutt temporary files.
published 2019-11-01 7 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2352
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
Mutt before 1.5.20 patch 7 allows an attacker to cause a denial of service via a series of requests to mutt temporary files.
Patch / fix
- mutt Debian 14, Debian 13, Debian 12 1.5.20-7
debian advisories DEBIAN-CVE-2005-2351
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2005-2351 updated cvss 5.5
mutt: denial of service via a series of requests to temporary files
-
Red Hat Enterprise Linux 5 mutt Red Hat Enterprise Linux 6 muttaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 mutt Red Hat Enterprise Linux 8 muttnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- mutt mutt
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
security-tracker.debian.org
/tracker/CVE-2005-2351
third-party-advisory
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=311296
mailing-list, third-party-advisory
Sources
- CVE List CVE-2005-2351
- NVD CVE-2005-2351
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.