// back

Multiple Vendor libexif Integer Overflow Heap Corruption Vulnerability



Exchangeable image file format (Exif) is an industry standard image tagging technology used by many digital camera devices. libexif is an open source library for handling the Exif format. More information can be found at the URLs shown below.



Remote exploitation of an integer overflow vulnerability in libexif, as included in various vendors' operating system distributions, could allow attackers to crash the process or execute arbitrary code.

The problem manifests when parsing a tagged image with a large number of Exif components. Applications using this library are susceptible to a heap overflow when an integer overflow is triggered in the exif_data_load_data_entry function.


Exploitation requires that a targeted user process a malicious image using one of several available tools that utilize libexif for Exif tag parsing. These tools include, but are not limited to, several applications included in the GNOME and KDE desktops.


iDefense confirmed the existence of this vulnerability in versions 0.6.13 through 0.6.15 of libexif.


iDefense is currently unaware of any workarounds for this issue.


The libexif maintainers have released version 0.6.16 of libexif to address this vulnerability.


The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2006-4168 to this issue. This is a candidate for inclusion in the CVE list (http://cve.mitre.org/), which standardizes names for security problems.


08/16/2006 Initial vendor notification
06/05/2007 Second vendor notification
06/11/2007 Initial vendor response
06/13/2007 Coordinated public disclosure


This vulnerability was discovered by Sean Larsson (iDefense Labs).

Get paid for vulnerability research

Free tools, research and upcoming events


Copyright © 2007 Verisign, Inc.

Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDefense. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please e-mail customer service for permission.

Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.