CVE-2014-0467
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer overflow in copy.c in Mutt before 1.5.23 allows remote attackers to cause a denial of service (crash) via a crafted RFC2047 header line, related to address expansion.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBuffer overflow in Mutt's copy.c file (versions before 1.5.23) allows remote attackers to cause a denial of service via a crafted RFC2047 header line. The vulnerability occurs during address expansion when parsing malformed headers, leading to a buffer overflow that can crash the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.5.22= 1.5= 1.5.1= 1.5.2= 1.5.3= 1.5.4= 1.5.5= 1.5.6= 1.5.7= 1.5.8= 1.5.9= 1.5.10= 11.4= 12.3= 13.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Mutt is installedRun 'which mutt' on Linux/Unix systems, or check package manager: 'dpkg -l | grep -i mutt' (Debian/Ubuntu), 'rpm -qa | grep -i mutt' (RHEL/CentOS), or 'zypper se mutt' (SUSE)Affected if Mutt is found on the system
-
Determine installed Mutt versionRun 'mutt -v' or 'mutt --version' to display the version string. On SUSE, use 'rpm -q mutt' to get the package versionAffected if Version output is displayed
-
Compare version against affected rangeExamine the version number from step 2. The affected versions are: 1.5.22 and earlier, or specifically 1.5 through 1.5.10 inclusive. The fixed version is 1.5.23Affected if Version is 1.5.22, 1.5.21, 1.5.20, 1.5.19, 1.5.18, 1.5.17, 1.5.16, 1.5.15, 1.5.14, 1.5.13, 1.5.12, 1.5.11, 1.5.10, or any 1.5.x version at or below 1.5.22
-
Check OpenSUSE package versions (if applicable)If running OpenSUSE 11.4, 12.3, or 13.1, use 'rpm -q mutt' to confirm the shipped Mutt version is below 1.5.23Affected if System is OpenSUSE 11.4, 12.3, or 13.1 and ships a vulnerable Mutt version
The system is affected if Mutt version 1.5.22 or any earlier 1.5.x release (1.5 through 1.5.10) is installed, or if running OpenSUSE 11.4, 12.3, or 13.1 with the distribution-supplied Mutt package.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Mutt 1.5.23 or later to patch the buffer overflow in RFC2047 header parsing. Alternatively, sanitize or filter potentially malicious email headers at the MTA level before delivery.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0467 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data