# CVE-2003-0021: Path traversal in n/a

> Attackers can overwrite arbitrary files by tricking users into viewing malicious terminal escape sequences in Eterm.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0021, GHSA-v6jh-gv6q-3h4r

## What is CVE-2003-0021?

CVE-2003-0021 is a medium-severity path traversal vulnerability in n/a, published on 1 Sep 2004. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The "screen dump" feature in Eterm 0.9.1 and earlier allows attackers to overwrite arbitrary files via a certain character escape sequence when it is echoed to a user's terminal, e.g. when the user views a file containing the malicious sequence.

## Which versions are affected by CVE-2003-0021?

It affects 1 product.


Products: Michael Jennings Eterm.

## How do I fix CVE-2003-0021?

Upgrade to a fixed version.

## Is CVE-2003-0021 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0068](https://insights.sbomify.com/CVE-2003-0068/): Command injection in n/a (high 7.5)
- [CVE-2000-0367](https://insights.sbomify.com/CVE-2000-0367/): Privilege escalation in n/a (high 7.2)
- [CVE-2000-0476](https://insights.sbomify.com/CVE-2000-0476/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0021 and fix it if it is affected.

What it is: CVE-2003-0021 is a medium-severity path traversal vulnerability in n/a, published on 1 Sep 2004. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2003-0021 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-2003-0021/ (Markdown: https://insights.sbomify.com/CVE-2003-0021/index.md)
```

## Sources

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

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