# CVE-2003-0024: Command injection in n/a

> Attackers can execute arbitrary commands by exploiting a character escape sequence in the aterm terminal emulator's menuBar feature.

- **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:** 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-jp38-6jm8-629g

## What is CVE-2003-0024?

CVE-2003-0024 is a high-severity command injection 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 menuBar feature in aterm 0.42 allows attackers to modify menu options and execute arbitrary commands via a certain character escape sequence that inserts the commands into the menu.

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

It affects 1 product.


Products: Aterm Aterm.

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

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

## Is CVE-2003-0024 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0067](https://insights.sbomify.com/CVE-2003-0067/): Command injection in n/a (high 7.5)
- [CVE-2008-1142](https://insights.sbomify.com/CVE-2008-1142/): Security feature bypass in n/a (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0024 is a high-severity command injection 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-0024 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-0024/ (Markdown: https://insights.sbomify.com/CVE-2003-0024/index.md)
```

## Sources

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

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