The TIFFFdOpen function in tif_unix.c in LibTIFF 4.0.10 has a memory leak, as demonstrated by pal2rgb.
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Link | Tags |
---|---|
https://usn.ubuntu.com/3906-1/ | third party advisory vendor advisory |
http://bugzilla.maptools.org/show_bug.cgi?id=2836 | issue tracking exploit third party advisory |
https://usn.ubuntu.com/3906-2/ | third party advisory vendor advisory |
http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00041.html | mailing list third party advisory vendor advisory |
https://gitlab.com/libtiff/libtiff/commit/0c74a9f49b8d7a36b17b54a7428b3526d20f88a8 | third party advisory patch |
https://seclists.org/bugtraq/2019/Nov/5 | third party advisory mailing list |
http://packetstormsecurity.com/files/155095/Slackware-Security-Advisory-libtiff-Updates.html | vdb entry third party advisory |
https://lists.debian.org/debian-lts-announce/2019/11/msg00027.html | third party advisory mailing list |
https://security.gentoo.org/glsa/202003-25 | third party advisory vendor advisory |