# CVE-1999-0365: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in mailcap entries, requiring user interaction to process malicious mail.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-gmgp-r787-3hjp

## What is CVE-1999-0365?

CVE-1999-0365 is a high-severity command injection vulnerability in n/a, published on 29 Sep 1999. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The metamail package allows remote command execution using shell metacharacters that are not quoted in a mailcap entry.

## Which versions are affected by CVE-1999-0365?

It affects 2 products.


Products: Metainfo Metaip, Metainfo Sendmail.

## How do I fix CVE-1999-0365?

No fix has been published for CVE-1999-0365 yet. Limit exposure of the affected software until one is available.

## Is CVE-1999-0365 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0365 and fix it if it is affected.

What it is: CVE-1999-0365 is a high-severity command injection vulnerability in n/a, published on 29 Sep 1999. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-1999-0365 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-1999-0365/ (Markdown: https://insights.sbomify.com/CVE-1999-0365/index.md)
```

## Sources

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

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