Skip to content
Noroxi
CVE-2018-14355· NVD / CVE Program· CNA mitre

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/util.c mishandles ".." directory traversal in a mailbox name.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Jul 17, 2018
Updated
Jun 16, 2026
EPSS
3.3% · 88th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.3%

Affected systems

VendorProduct
muttmutt
debiandebian linux
neomuttneomutt
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux16.04
  • debian debian linux8.0
  • debian debian linux9.0
  • mutt muttbefore 1.10.1
  • neomutt neomuttbefore 20180716

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.5muttbefore 1.10.1-r01.10.1-r0
Debian:12muttbefore 1.10.1-11.10.1-1
Debian:12neomuttbefore 20180716+dfsg.1-120180716+dfsg.1-1
Debian:8muttbefore 1.5.23-3+deb8u11.5.23-3+deb8u1
Debian:9muttbefore 1.7.2-1+deb9u11.7.2-1+deb9u1
openSUSE:Tumbleweedmuttbefore 2.0.7-2.22.0.7-2.2
openSUSE:Tumbleweedneomuttbefore 20210205-3.320210205-3.3
Red Hat:enterprise_linux:7::clientmuttbefore 5:1.5.21-29.el75:1.5.21-29.el7
Red Hat:enterprise_linux:7::clientmutt-debuginfobefore 5:1.5.21-29.el75:1.5.21-29.el7
SUSE:Linux Enterprise Desktop 12 SP3muttbefore 1.10.1-55.3.11.10.1-55.3.1
SUSE:Linux Enterprise Desktop 12 SP3muttbefore 1.10.1-55.6.11.10.1-55.6.1
SUSE:Linux Enterprise Module for Basesystem 15muttbefore 1.10.1-3.3.41.10.1-3.3.4
SUSE:Linux Enterprise Point of Sale 11 SP3muttbefore 1.5.17-42.43.11.5.17-42.43.1

Same product

mutt: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-14354An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.
    41Plan
  • CVE-2018-14362An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.
    40Plan
  • CVE-2018-14359An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.
    40Plan
  • CVE-2018-14358An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.
    40Plan
  • CVE-2018-14357An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.
    40Plan
  • CVE-2018-14356An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:mutt1.10.1-r0 · Alpine:v3.5Package registry (OSV)
debian:mutt1.10.1-1 · Debian:12Package registry (OSV)
debian:neomutt20180716+dfsg.1-1 · Debian:12Package registry (OSV)
opensuse:mutt2.0.7-2.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:neomutt20210205-3.3 · openSUSE:TumbleweedPackage registry (OSV)
red hat:mutt5:1.5.21-29.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:mutt-debuginfo5:1.5.21-29.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:mutt1.10.1-55.3.1 · SUSE:Linux Enterprise Desktop 12 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records