CVE-2004-2167 in the critical feed json
Multiple buffer overflows in LaTeX2rtf 1.9.15, and possibly other versions, allow remote attackers to execute arbitrary code via (1) the ex…
published 2004-12-31 21 y ago modified 2026-06-16 4 mo ago also EUVD-2004-2159
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.3%
- EPSS 14.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Multiple buffer overflows in LaTeX2rtf 1.9.15, and possibly other versions, allow remote attackers to execute arbitrary code via (1) the expandmacro function, and possibly (2) Environments and (3) TranslateCommand.
Patch / fix
- latex2rtf Debian 14, Debian 13, Debian 12 1.9.16
debian advisories DEBIAN-CVE-2004-2167
Timeline
- First public exploit (EDB-24622)
- Published
Exploit prediction
14.31% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-24622 LaTeX2rtf 1.9.15 - Remote Buffer Overflow remote, 2004-09-21
- securitytracker.com http://www.securitytracker.com/alerts/2004/Sep/1011367.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/11233 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
securitytracker.com
/alerts/2004/Sep/1011367.html
vdb-entry, exploit
-
securityfocus.com
/bid/11233
vdb-entry, exploit, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/17487
vdb-entry
- cvs.sourceforge.net /viewcvs.py/latex2rtf/latex2rtf/definitions.c?rev=1.22&view=log
-
osvdb.org
/displayvuln.php?osvdb_id=10216
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/17460
vdb-entry
Sources
- CVE List CVE-2004-2167
- NVD CVE-2004-2167
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.