Bug 1325090 (CVE-2016-3624) - CVE-2016-3624 libtiff: out of bounds write in the rgb2ycybr tool
Summary: CVE-2016-3624 libtiff: out of bounds write in the rgb2ycybr tool
Alias: CVE-2016-3624
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 1316881
TreeView+ depends on / blocked
Reported: 2016-04-08 08:09 UTC by Andrej Nemec
Modified: 2021-02-17 04:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-05-11 10:18:09 UTC

Attachments (Terms of Use)

Description Andrej Nemec 2016-04-08 08:09:17 UTC
Out of bounds write vulnerability was found in cvtClump function in rgb2ycybr.c, allowing attacker to cause a denial of service via a crafted TIFF image.

Vulnerable code:


187         lumaGreen[TIFFGetG(RGB)] +
188         lumaBlue[TIFFGetB(RGB)];
189     /* accumulate chrominance */
190     Cb += (TIFFGetB(RGB) - Y) * D1;
191     Cr += (TIFFGetR(RGB) - Y) * D2;
192     /* emit luminence */
193     *op++ = V2Code(Y,
194         refBlackWhite[0], refBlackWhite[1], 255);
195                 }

Public via:


Comment 1 Andrej Nemec 2016-04-08 08:10:20 UTC

Name: Mei Wang (Qihoo 360)

Comment 3 Stefan Cornelius 2017-05-11 10:18:09 UTC
The command line parameters passed to the tool influence the calculations within the cvtRaster() function in gb2ycbcr.c. This can lead to a call to _TIFFmalloc() with a bogus size. If this allocation fails, NULL is returned. The application doesn't check for this condition, which ultimately leads to an access violation when the cvtClump() function tries to write "into" it.

I've not really investigated what happens if the allocation succeeds - worst case could be a memory corruption, but since this issue depends on far-fetched custom command line parameters, I consider the likelyhood and impact of this to be minimal.

Comment 4 Stefan Cornelius 2017-05-11 10:18:18 UTC
External References:


Comment 5 Stefan Cornelius 2017-05-11 10:18:24 UTC

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.