Skip to content
Fencer Intel
medium 4.3

CVE-2011-2485 json

The gdk_pixbuf__gif_image_load function in gdk-pixbuf/io-gif.c in gdk-pixbuf before 2.23.5 does not properly handle certain return values,…

published 2012-07-03 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2473

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

Summary

The gdk_pixbuf__gif_image_load function in gdk-pixbuf/io-gif.c in gdk-pixbuf before 2.23.5 does not properly handle certain return values, which allows remote attackers to cause a denial of service (memory consumption) via a crafted GIF image file.

Patch / fix

  • gdk-pixbuf Debian 14, Debian 13, Debian 12 2.23.3-3.1

debian advisories DEBIAN-CVE-2011-2485

  • gdk-pixbuf openSUSE Tumbleweed 2.36.0-1.1

opensuse advisories openSUSE-SU-2024:10453-1

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-2011-2485 updated cvss 4.3

gdk-pixbuf: incorrect error detection in the GIF image loader

  • Red Hat Enterprise Linux 4 gtk2, evolution28-gtk2 Red Hat Enterprise Linux 5 gtk2, pidgin Red Hat Enterprise Linux 6 gtk2, finch, pidgin, libpurple, pidgin-perl, libpurple-tcl, +3 more
    affected: no fix available
  • Red Hat Enterprise Linux 4 frysk, gdk-pixbuf Red Hat Enterprise Linux 5 gdk-pixbuf
    under investigation

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

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

Exploits and checks

  • git.gnome.org http://git.gnome.org/browse/gdk-pixbuf/commit/?id=f8569bb13e2aa1584dde61ca545144750f7a7c98 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

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.