Bugzilla – Bug 1016589
VUL-0: imagemagick: Check validity of extend during TIFF file reading
Last modified: 2017-06-08 11:04:41 UTC
Ref: http://seclists.org/oss-sec/2016/q4/713 ============================================== Debian bug: https://bugs.debian.org/845198 Reference URL: https://security-tracker.debian.org/845198 Upstream commit: https://github.com/ImageMagick/ImageMagick/commit/2bb6941a2d557f26a2f2049ade466e118eeaab91 Upstream issue: N/A Upstream version fixed: 6.9.5-1 ==============================================
bugbot adjusting priority
Sadly the upstream commit says nothing about the semantics of the moved code block. The dependency to the code in-between the old and new location is not obvious to me. Maybe the initialization of the colormap is the thing that needs to be done first. ImageMagick: [n/a] SLE-12:Update at coders/tiff.c:1082 the call to SetImageExtent is not present at all nothing similar to be found [unclear] SLE-11:Update at coders/tiff.c:926 here is a call to SetImageExtent but with zero columns/rows [n/a] openSUSE:13.2:Update at coders/tiff.c:3671 the call to SetImageExtent is not present at all nothing similar to be found GraphicsMagick: [n/a] SLE-11:Update at coders/tiff.c:1485 the call to SetImageExtent is not present at all nothing similar to be found [n/a] openSUSE:13.2:Update at coders/tiff.c:1627 the call to SetImageExtent is not present at all nothing similar to be found [n/a] openSUSE:Leap:42.1:Update at coders/tiff.c:1898 the call to SetImageExtent is not present at all nothing similar to be found [n/a] openSUSE:Leap:42.2:Update at coders/tiff.c:1924 the call to SetImageExtent is not present at all nothing similar to be found
all ImageMagick issues from one oss posting were opened twice *** This bug has been marked as a duplicate of bug 1017320 ***