dbcve.org
Imlib2Application · Enlightenment

CVE-2008-6079

HIGH · 10.0 CVSS v2.0 Published 2009-02-06
Fix available
A fix is available. Upgrade to after 1.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
imlib2 before 1.4.2 allows context-dependent attackers to have an unspecified impact via a crafted (1) ARGB, (2) BMP, (3) JPEG, (4) LBM, (5) PNM, (6) TGA, or (7) XPM file, related to "several heap and stack based buffer overflows - partly due to integer overflows."

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 confidence

imlib2 before 1.4.2 contains multiple buffer overflow vulnerabilities in its image file parsing code for ARGB, BMP, JPEG, LBM, PNM, TGA, and XPM formats. The vulnerabilities are caused by integer overflows that lead to heap and stack-based buffer overflows when processing crafted image files, allowing context-dependent attackers to potentially execute arbitrary code or cause denial of service.

MitigationUpgrade imlib2 to version 1.4.2 or later to patch the vulnerabilities. Avoid processing untrusted or unknown image files with vulnerable versions until the upgrade is applied.

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
Imlib2Application
Affected:<= 1.4.1= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.1= 1.1.1= 1.1.2= 1.2.1= 1.2.2

CVSS 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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify imlib2 is installed
    Run 'pkg-config --modversion imlib2' or check for the library file (typically libimlib2.so) in /usr/lib or /usr/lib64
    Affected if imlib2 is not found, the system is not affected by this CVE
  2. Determine the installed imlib2 version
    Use 'imlib2-config --version' or check the package manager (e.g., 'rpm -q imlib2' for RHEL-based systems, 'dpkg -l libimlib2' for Debian-based)
    Affected if version cannot be determined or is older than 1.4.2
  3. Compare installed version against affected range
    Compare the version found in step 2 to the affected versions: 1.0 through 1.2.2, 1.0.x series, 1.1.x series, 1.2.x series, or any version <= 1.4.1
    Affected if the installed version matches any of these affected versions (1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.1, 1.1.1, 1.1.2, 1.2.1, 1.2.2, or <=1.4.1)
  4. Identify if vulnerable image formats are processed
    Review applications or services that use imlib2 to load user-supplied or network-supplied image files in any of these formats: ARGB, BMP, JPEG, LBM, PNM, TGA, or XPM
    Affected if applications process these image formats from untrusted sources and imlib2 version is affected

The environment is affected if imlib2 version 1.4.1 or earlier (including 1.0.x, 1.1.x, and 1.2.x series) is installed and used to process image files in ARGB, BMP, JPEG, LBM, PNM, TGA, or XPM formats.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.1
Interim mitigation

Upgrade imlib2 to version 1.4.2 or later to patch the vulnerabilities. Avoid processing untrusted or unknown image files with vulnerable versions until the upgrade is applied.

Recommended fix High confidence

1.4.2 or later

  1. Check the currently installed version of imlib2 using your system's package manager or by running 'imlib2_config --version' or checking your package database
  2. Upgrade imlib2 to version 1.4.2 or later. For Debian/Ubuntu systems: run 'apt-get update && apt-get install libimlib2' or 'apt-get upgrade libimlib2'. For Red Hat/Fedora systems: run 'yum update imlib2' or 'dnf update imlib2'. For source compilation: download imlib2 1.4.2 or later from the official source and compile with standard ./configure && make && make install
  3. Verify the new version is installed by running 'imlib2_config --version' or checking the package version again
Caveat Likely minimal; imlib2 1.4.2 is a minor version update focused on security fixes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Imlib2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-6079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-6079 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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