libexif Buffer Overflow in Processing EXIF Headers May Let Remote Users Crash the Application or Execute Arbitrary Code
|
|
SecurityTracker Alert ID: 1013398
|
|
SecurityTracker URL: http://securitytracker.com/id?1013398
|
|
CVE Reference: CVE-2005-0664
(Links to External Site)
|
Updated: Jun 13 2007
|
Original Entry Date: Mar 8 2005
|
Impact: Denial of service via network, Execution of arbitrary code via network, User access via network
|
Fix Available: Yes
Vendor Confirmed: Yes
|
Version(s): 0.6.9 and prior versions
|
Description: A buffer overflow vulnerability was reported in libexif. A remote user may be able to cause a target user's application to crash or execute arbitrary code.
The exif library does not properly validate user-supplied input in several places. A remote user can create a specially crafted
JPEG image with invalid EXIF header data. When the image is loaded by the target user's application that uses libexif, the application
may crash or potentially execute arbitrary code.
The flaw resides in 'exif-data.c'.
Sylvain Defresne discovered this vulnerability.
|
Impact: A remote user can create an image file that, when loaded by the target user's application, will cause the application to crash or potentially execute arbitrary code.
|
Solution: The vendor has issued a patch, available at:
http://sourceforge.net/tracker/download.php?group_id=12272&atid=312272&file_id=124506&aid=1158402
The
vendor's bug report is available at:
http://sourceforge.net/tracker/index.php?func=detail&aid=1158402&group_id=12272&atid=312272
|
Vendor URL: sourceforge.net/projects/libexif/ (Links to External Site)
|
Cause: Boundary error
|
Underlying OS: Linux (Any), UNIX (Any)
|
|
Message History:
This archive entry has one or more follow-up message(s) listed below.
|
Source Message Contents
|
Date: Tue, 8 Mar 2005 01:59:21 -0500
Subject: [none]
|
Sylvain Defresne reported:
> The exif library fails to validate input in several place, and
> jpeg image with invalid exif data may crash user application.
>
> The attached patch fixes some obvious improper access to data
> without checking boundary. There may be others that I have not
> found (as I have just given it a quick look to correct a crash
> caused by some of my images).
CVE: CAN-2005-0664
|
|
