[REGRESSION] Predictor tag fails to be written correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tiff (Ubuntu) |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Lucid |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Precise |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Trusty |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Utopic |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Vivid |
Fix Released
|
Undecided
|
Marc Deslauriers |
Bug Description
The patch debian/
It seems the data is correctly saved, but the "predictor" tag is not, which prevents reading the data correctly again.
This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty (release 4.0.3-7ubuntu0.2).
I'm attaching an example TIFF file "small.tiff" for showing the behaviour. It is compressed in LZW without predictor, so it is written/read correctly.
However, if you recompress it with this command, the error happens:
$ tiffcp -c lzw:2 small.tiff small-c2.tiff
Then displaying it in eog shows a completely different image. Tiffinfo indicates a problem with the tags:
$ tiffinfo small-c2-bad.tiff | grep Predictor
TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered.
Comparing it with a good version of the file (generated with a previous version of libtiff):
$ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)
$ tiffcmp small-c2.tiff small-c2-good.tiff
TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered.
Predictor tag appears only in small-c2-good.tiff
Changed in tiff (Ubuntu Lucid): | |
status: | New → Confirmed |
Changed in tiff (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in tiff (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in tiff (Ubuntu Utopic): | |
status: | New → Confirmed |
Changed in tiff (Ubuntu Vivid): | |
status: | New → Confirmed |
tags: | added: regression-update |
After a few trial and error session, I think the attached patch to replace debian/ patches/ CVE-2014- 8128-5. patch should fix this reported problem.