tif_write.c in libtiff 4.0.6 has an issue in the error code path of TIFFFlushData1() that didn't reset the tif_rawcc and tif_rawcp members. Reported as MSVR 35095, aka "TIFFFlushData1 heap-buffer-overflow."
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/94743 | vdb entry |
| https://github.com/vadz/libtiff/commit/83a4b92815ea04969d494416eaae3d4c6b338e4a#diff-5be5ce02d0dea67050d5b2a10102d1ba | exploit third party advisory patch |
| http://rhn.redhat.com/errata/RHSA-2017-0225.html | vendor advisory |
| http://www.securityfocus.com/bid/94484 | vdb entry third party advisory |
| http://www.debian.org/security/2017/dsa-3762 | vendor advisory |