CVE-2015-4491
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInteger overflow in the make_filter_table function in pixops/pixops.c in gdk-pixbuf before 2.31.5, as used in Mozilla Firefox before 40.0 and Firefox ESR 38.x before 38.2 on Linux, Google Chrome on Linux, and other products, allows remote attackers to execute arbitrary code or cause a denial of service (heap-based buffer overflow and application crash) via crafted bitmap dimensions that are mishandled during scaling.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInteger overflow in gdk-pixbuf's make_filter_table function allows attackers to trigger a heap-based buffer overflow by providing crafted bitmap dimensions that cause incorrect calculation of buffer sizes during image scaling operations, potentially enabling arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.04= 14.04= 15.04= 21= 22<= 2.31.4= 10= 11.3= 13.1= 13.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if gdk-pixbuf library is installedRun 'dpkg -l | grep gdk-pixbuf' on Debian/Ubuntu, 'rpm -qa | grep gdk-pixbuf' on Fedora/RHEL, or 'pkg_info | grep gdk-pixbuf' on Solaris. Alternatively, check for the library file: 'ls /usr/lib/*/libgdk_pixbuf-2.0.so*' or 'ldconfig -p | grep gdk_pixbuf'.Affected if gdk-pixbuf is not installed at all, the system is not affected by this specific vulnerability in the library.
-
Determine the installed gdk-pixbuf versionRun 'dpkg -s libgdk-pixbuf2.0-dev' (Ubuntu), 'rpm -q gdk-pixbuf2' (Fedora), 'pkg_info -a | grep gdk-pixbuf' (Solaris), or check the library file version with 'strings /usr/lib/*/libgdk_pixbuf-2.0.so.0 | grep -i version' or 'gdk-pixbuf-csource --version'. Compare the version number against the affected range: versions <= 2.31.4 are vulnerable.Affected if The installed version is 2.31.4 or lower.
-
Identify applications or processes using gdk-pixbuf for image scalingReview which applications on the system commonly link against gdk-pixbuf for image handling, such as image viewers, web browsers, or GTK-based applications. Check with 'ldd /path/to/binary | grep gdk_pixbuf' or 'lsof | grep gdk_pixbuf' for running processes using the library.Affected if Applications that perform image scaling operations using gdk-pixbuf are in use, and the library version is <= 2.31.4.
-
Inspect if any user-supplied or remote images with unusual dimensions are being processedCheck application logs, proxy logs, or file upload directories for image files that may have abnormally large or crafted width/height values in their headers. For web-serving applications, review access logs for image processing requests.Affected if There is evidence of image files with specially crafted dimensions being processed by a vulnerable version of gdk-pixbuf.
A system is affected if gdk-pixbuf version 2.31.4 or earlier is installed and any application uses it to scale images with user-controlled dimensions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate gdk-pixbuf to version 2.31.5 or later, which contains the fix for the integer overflow in dimension handling. For applications like Firefox or Chrome, ensure they link against a patched version of the library.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4491 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.mozilla.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- www.oracle.com
- www.oracle.com
- www.ubuntu.com
- www.ubuntu.com
- bugzilla.gnome.org
- bugzilla.mozilla.org
- bugzilla.redhat.com
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.securitytracker.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- www.ubuntu.com
- git.gnome.org
- security.gentoo.org
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-4491 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data