Skip to content
Fencer Vulns
critical 10.0

CVE-2009-1382 json

Multiple stack-based buffer overflows in mimetex.cgi in mimeTeX, when downloaded before 20090713, allow remote attackers to execute arbitra…

published 2009-07-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1380

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.0%
EPSS 9.0% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Multiple stack-based buffer overflows in mimetex.cgi in mimeTeX, when downloaded before 20090713, allow remote attackers to execute arbitrary code via a TeX file with long (1) picture, (2) circle, or (3) input tags.

Patch / fix

  • mimetex Debian 14, Debian 12 1.50-1.1

debian advisories DEBIAN-CVE-2009-1382

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-1382 updated cvss 7.5

mimeTeX: various flaws

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.02% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • groups.google.com http://groups.google.com/group/comp.text.tex/browse_thread/thread/5d56d3d744351578 referenced PoC, tagged "exploit" by a source, unverified
  • scary.beasts.org http://scary.beasts.org/security/CESA-2009-009.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.