Skip to content
Fencer Intel
high 7.8

CVE-2018-16745 json

An issue was discovered in mgetty before 1.2.1.

published 2018-09-13 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-8545

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

An issue was discovered in mgetty before 1.2.1. In fax_notify_mail() in faxrec.c, the mail_to parameter is not sanitized. It could allow a buffer overflow if long untrusted input can reach it.

Patch / fix

  • mgetty_project mgetty 1.2.1
  • mgetty Debian 14, Debian 13, Debian 12 1.2.1-1

debian advisories DEBIAN-CVE-2018-16745

  • mgetty SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 1.1.36-58.3.1
  • mgetty SLE Module for Basesystem 15 1.1.37-3.3.2
  • mgetty SLES for SAP 11 SP4, SLES 11 SP4 1.1.36-28.3.1

suse advisories SUSE-SU-2018:2979-1SUSE-SU-2018:2894-1SUSE-SU-2018:2850-1

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-2018-16745 updated cvss 3.9

mgetty: Stack-based buffer overflow in fax_notify_mail() in faxrec.c

  • Red Hat Enterprise Linux 5 mgetty Red Hat Enterprise Linux 6 mgetty, mgetty-voice, mgetty-sendfax, mgetty-viewfax
    affected: workaround, no fix planned “Make sure the `notify` option in /etc/mgetty+sendfax/mgetty.config does not contain more than 150 characters and that the file is readable and writable only by root.”
  • Red Hat Enterprise Linux 7 mgetty, mgetty-voice, mgetty-sendfax, mgetty-viewfax
    affected: workaround, no fix available “Make sure the `notify` option in /etc/mgetty+sendfax/mgetty.config does not contain more than 150 characters and that the file is readable and writable only by root.”

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.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • x41-dsec.de https://www.x41-dsec.de/lab/advisories/x41-2018-007-mgetty referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.