VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

mgetty: vulnerability history, versions and safety

mgetty is a package in the Debian ecosystem. Vulert records 24 vulnerabilities for it across 4 affected ranges, from Jan 2003 to Jul 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
24 vulnerabilities recorded U24
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mgetty vulnerabilities

Vulert verdict on mgetty i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 24 Jul 2019. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 24 vulnerabilities on record across 16 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 24 over 16 years · 0 in the last year i
  • Latest disclosure 24 Jul 2019 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 1.2.1-1 (exclusive) 14
up to 1.1.36-1.3 (exclusive) 2
up to 1.1.30-1 (exclusive) 4
up to 1.1.29 (exclusive) 4

02 Disclosure history

How often vulnerabilities are recorded

  • 2003 8
  • 2008 2
  • 2018 10
  • 2019 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 24 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mgetty

The 5 most severe of 24 vulnerabilities recorded for this package

Search all 24 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Buffer Overflow Vulnerability in mgetty Package: CVE-2018-16745 7.8 high 1.2.1-1 13 Sep 2018
Stack-based Buffer Overflow in mgetty 7.8 high 1.2.1-1 13 Sep 2018
Stack-based Buffer Overflow in mgetty 7.8 high 1.2.1-1 13 Sep 2018
Command Injection Vulnerability in mgetty: CVE-2018-16741 7.8 high 1.2.1-1 13 Sep 2018
Command Injection Vulnerability in mgetty: CVE-2018-16744 7.8 high 1.2.1-1 13 Sep 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mgetty

Is mgetty safe to use?

Vulert records 24 vulnerabilities for mgetty in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 24 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does mgetty have?

24 vulnerabilities are recorded for mgetty in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 24 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mgetty vulnerabilities disclosed?

0 vulnerabilities were recorded for mgetty in the last 12 months, and the oldest entry in this database dates to 17 Jan 2003. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mgetty are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mgetty for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mgetty version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.