# CVE-2018-16744: Command injection in n/a

> Attackers can execute arbitrary commands via unsanitized mail_to parameter in mgetty's fax notification feature using popen.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-16744, GHSA-86wq-gv4v-p8jq, UBUNTU-CVE-2018-16744

## What is CVE-2018-16744?

CVE-2018-16744 is a high-severity command injection vulnerability in n/a, published on 13 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 for command injection if untrusted input can reach it, because popen is used.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-16744?

It affects 1 product.


Products: Mgetty Project Mgetty.

## How do I fix CVE-2018-16744?

Upgrade to a fixed version.

## Is CVE-2018-16744 being exploited?

There is no known exploitation of CVE-2018-16744 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-16742](https://insights.sbomify.com/CVE-2018-16742/): Memory corruption in n/a (high 7.8)
- [CVE-2018-16743](https://insights.sbomify.com/CVE-2018-16743/): Memory corruption in n/a (high 7.8)
- [CVE-2018-16745](https://insights.sbomify.com/CVE-2018-16745/): Memory corruption in n/a (high 7.8)
- [CVE-2019-1010189](https://insights.sbomify.com/CVE-2019-1010189/): Denial of service in mgetty (medium 5.5)
- [CVE-2019-1010190](https://insights.sbomify.com/CVE-2019-1010190/): Denial of service in mgetty (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16744 and fix it if it is affected.

What it is: CVE-2018-16744 is a high-severity command injection vulnerability in n/a, published on 13 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16744 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-16744/ (Markdown: https://insights.sbomify.com/CVE-2018-16744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16744
- OSV: https://osv.dev/vulnerability/CVE-2018-16744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-16744/
Summaries are generated and may contain mistakes; the official description above is the record.