Skip to content
Fencer Intel
critical 9.8

CVE-2018-14361 json

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

published 8y ago modified 4mo ago also EUVD-2018-6282

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

An issue was discovered in NeoMutt before 2018-07-16. nntp.c proceeds even if memory allocation fails for messages data.

Patch / fix

  • neomutt neomutt 20180716
  • mutt Debian 14, Debian 13, Debian 12 1.9.1-1
  • neomutt Debian 14, Debian 13, Debian 12 20180716+dfsg.1-1

debian advisories DEBIAN-CVE-2018-14361

  • neomutt Ubuntu Pro 18.04 LTS 20171215+dfsg.1-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2018-14361

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • mutt SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 1.10.1-55.6.1
  • mutt SLE Module for Basesystem 15 1.10.1-3.3.4
  • mutt SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 1.10.1-55.3.1

suse advisories SUSE-SU-2019:1196-1SUSE-SU-2018:2085-1SUSE-SU-2018:2084-1

  • mutt openSUSE Tumbleweed 2.0.7-2.2
  • neomutt openSUSE Tumbleweed 20210205-3.3

opensuse advisories openSUSE-SU-2024:11069-1openSUSE-SU-2024:11079-1

  • neomutt Arch Linux 20180716-1

arch linux advisories AVG-740

Is CVE-2018-14361 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.50% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel 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.