# CVE-2003-0079: Denial of service in n/a

> Attackers can cause a denial of service in the hanterm terminal emulator by sending a specific character escape sequence that triggers a tight loop.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-25m3-g4xm-g7jw

## What is CVE-2003-0079?

CVE-2003-0079 is a low-severity denial of service 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 DEC UDK processing feature in the hanterm (hanterm-xf) terminal emulator before 2.0.5 allows attackers to cause a denial of service via a certain character escape sequence that causes the terminal to enter a tight loop.

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

It affects 1 product.


Products: Hanterm Hanterm-Xf.

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

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

## Is CVE-2003-0079 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0077](https://insights.sbomify.com/CVE-2003-0077/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0079 is a low-severity denial of service 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-0079 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-0079/ (Markdown: https://insights.sbomify.com/CVE-2003-0079/index.md)
```

## Sources

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

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