# CVE-2002-1898: Command injection in n/a

> Remote attackers can execute arbitrary commands on macOS by tricking users into clicking a malicious telnet link in Terminal.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mw47-2hrx-68vv

## What is CVE-2002-1898?

CVE-2002-1898 is a high-severity command injection vulnerability in n/a, published on 28 Jun 2005. 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

Terminal 1.3 in Apple Mac OS X 10.2 allows remote attackers to execute arbitrary commands via shell metacharacters in a telnet:// link, which is executed by Terminal.app window.

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

## Which versions are affected by CVE-2002-1898?

It affects 1 product.


Products: Apple Terminal.

## How do I fix CVE-2002-1898?

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

## Is CVE-2002-1898 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1898 exists.

Public exploit code:

- Apple Mac OSX 10.2 - Terminal.APP Telnet Link Command Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1898 and fix it if it is affected.

What it is: CVE-2002-1898 is a high-severity command injection vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1898 exists.

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-2002-1898/ (Markdown: https://insights.sbomify.com/CVE-2002-1898/index.md)
```

## Sources

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

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