# CVE-2004-1293: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted RTF file with the rtf2latex2e converter.

- **Severity:** Critical 10.0 (`AV:N/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:** 22 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-684j-4mgj-x6g7

## What is CVE-2004-1293?

CVE-2004-1293 is a critical memory corruption vulnerability in n/a, published on 22 Dec 2004. 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

Buffer overflow in the ReadFontTbl function in reader.c for rtf2latex2e 1.0fc2 allows remote attackers to execute arbitrary code via a crafted RTF file.

## Which versions are affected by CVE-2004-1293?

It affects 1 product.


Products: Rtf2latex2e Rtf2latex2e.

## How do I fix CVE-2004-1293?

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

## Is CVE-2004-1293 being exploited?

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

Public exploit code:

- RTF2LATEX2E 1.0 - Remote Stack Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1293 and fix it if it is affected.

What it is: CVE-2004-1293 is a critical memory corruption vulnerability in n/a, published on 22 Dec 2004. 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-2004-1293 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-2004-1293/ (Markdown: https://insights.sbomify.com/CVE-2004-1293/index.md)
```

## Sources

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

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