Skip to content
Fencer Intel
medium 6.8

CVE-2009-5018 json

Stack-based buffer overflow in gif2png.c in gif2png 2.5.3 and earlier might allow context-dependent attackers to execute arbitrary code via…

published 15y ago modified 4mo ago also EUVD-2009-4976

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.9%
EPSS 10.9% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Stack-based buffer overflow in gif2png.c in gif2png 2.5.3 and earlier might allow context-dependent attackers to execute arbitrary code via a long command-line argument, as demonstrated by a CGI program that launches gif2png.

Patch / fix

Is CVE-2009-5018 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-5018 updated

gif2png: command-line buffer overflow problem

  • 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

Timeline

  1. First public exploit (EDB-34356)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-34356 gif2png 2.5.2 - Remote Buffer Overflow dos, 2009-12-12
  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=547515 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

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

References

Sources

Fencer Intel 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.