exiv2 0.17 (from ubuntu8.10) and linked Software (such as digikam, gimp/ufraw) crashed (vendor confirmed bug, update available)

Bug #292780 reported by joerg
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
exiv2 (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Intrepid by Niels Kristian Bech Jensen

Bug Description

exiv2 (0.17) crashed reproducable (e.g. when opening a Nikon-Raw-File (*NEF), which has been modified by NikonCaptureNX). All software-programms using exiv2 (such as digikam, ufraw, GIMP) crash during startup or during loading these files , or get stability-problems (Gimp, opening Nikon-Raw-Files via "gimp-ufraw")

Denial of Service possible

exiv2 (0.17.1) do not have these problems.

---
# exiv2 *165.NEF
Warning: Directory ImageSubIfd0 has an unhandled next pointer.
Warning: Directory ImageSubIfd1 has an unhandled next pointer.
Segmentation fault
#
---

from changelog of exiv2 (www.exiv2.org)
changes from version 0.17 to 0.17.1
-----------------------------------

* Exiv2 library
 - 0000560: [xmp] Can't delete (last) XMP tag. (Reported by SerGioGioGio)
 - 0000559: [exif] Crash when extracting Exif orientation flag from Kodak
            DCR raw file. (Reported by Gilles Caulier)
 - 0000558: [jpeg i/o] "Warning: JPEG format error, rc = 5" for most of my
            JPEG files. (Reported with patch by Marcus Holland-Moritz)
 - 0000552: [build environment] Build failure under Mac OS X 10.3.9
            (Reported by Marius Schamschula)
 - [exif] Fixed several potential division by 0 bugs.

joerg (joergfichtner)
description: updated
Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

I can confirm that.

Some files (not all - depends on what is modified, I presume) after modified using Nikon's CaptureNx causes libkexiv2 (based on exiv2 0.17) to crash on scanning for new images using Digikam.

Some of them, even after modified like above, shows the warning message but does not crash with segmentation fault.

Same behavior using #exiv2 xxx.nef and opening using Ufraw.

Revision history for this message
joerg (joergfichtner) wrote :

Hi cascagrossa
my workaround for this problem is (until the packages gets updated) :
Please care, that you do make a copy of all "productive" files before overwriting them!!!

- download source-code from exiv2-Homepage (http://www.exiv2.org/exiv2-0.17.1.tar.gz)
(Hint: Do NOT store it on a NTFS-Partition, it will not compile correctly. It took me some days to find out!!)
- gunzip exiv* ; tar xvf *
- cd exiv2-0.17.1
- ./configure --prefix $HOME/exiv2-0.17.1
- make ; make install
- save /usr/lib/libexiv2.so.4 (it's a symlink)
- copy new library (via sudo or as root): cp $HOME/exiv2-0.17.1/lib/libexiv2.so.4.0.1 /usr/lib
-save old binary (/usr/bin/exiv2), and
- copy new binary cp $HOME/exiv2.017.1/bin/exiv2 /usr/bin

start digikam, it will now start up correctly, and show all pictures correctly.
When starting digikam on a console, you'll see the failures, which probably have caused the crash of the buggy exiv2 (0.17). Even a lot of exiv-informations are displayed in digikam (I did not check, if some infos are missing).
--- snip ---
Warning: Directory ImageSubIfd0 has an unhandled next pointer.
Warning: Size 5308 of Exif.Nikon3.0x0091 exceeds 4096 bytes limit. Not decoded.
--- snap ---

Revision history for this message
joerg (joergfichtner) wrote :

sorry, forgot to mention, that the symlink for the library has to be set new ...

as root (or via sudo):;ln -s /usr/lib/libexiv2.so.4.0.1 /usr/lib/libexiv2.so.4

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Hi joerg,

At this moment I'm reinstalling the system (I broke it - my fault). I will try as soon as possible and post feedback on it.

Thanks in advance for the workaround.

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

sorry, but I decided to revert back to Hardy where this and a lot of other problems doesn't exist May be will try 9.04... that I hope will have less bugs...

Revision history for this message
Niels Kristian Bech Jensen (nkbjensen) wrote :

I have been hit by the other bug fixed in 0.17.1 (the crash with Kodak DCR files). Please update the package to the 0.17.1 point release.

Changed in exiv2:
status: New → Confirmed
Revision history for this message
Luka Renko (lure) wrote :

Can somebody test this in Jaunty/RC with updated exiv2 0.18.0?

Changed in exiv2 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Niels Kristian Bech Jensen (nkbjensen) wrote :

Only version 0.17 is affected by this bug. It is fixed in 0.17.1 and later versions, i.e. it is fixed in Jaunty.

Changed in exiv2 (Ubuntu):
status: Incomplete → Confirmed
Mark Purcell (msp)
Changed in exiv2 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.