First published: Sat Jan 26 2019(Updated: )
libvips before 8.7.4 generates output images from uninitialized memory locations when processing corrupted input image data because iofuncs/memory.c does not zero out allocated memory. This can result in leaking raw process memory contents through the output image.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/vips | 8.7.4-1+deb10u1 8.10.5-2 8.14.1-3+deb12u1 8.15.1-1 8.15.2-1 | |
ubuntu/vips | <8.4.5-1ubuntu0.1~ | 8.4.5-1ubuntu0.1~ |
ubuntu/vips | <8.7.4-1 | 8.7.4-1 |
ubuntu/vips | <8.2.2-1ubuntu0.1~ | 8.2.2-1ubuntu0.1~ |
LibVIRT | <8.7.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-6976 is a vulnerability in libvips before version 8.7.4 that allows the generation of output images from uninitialized memory locations when processing corrupted input image data.
CVE-2019-6976 affects libvips versions up to and excluding 8.7.4.
CVE-2019-6976 has a severity value of 5.3, which is considered medium.
To fix CVE-2019-6976, you should update to version 8.7.4-1 for Ubuntu or apply the recommended updates for the affected package on Debian.
You can find more information about CVE-2019-6976 in the references provided: https://blog.silentsignal.eu/2019/04/18/drop-by-drop-bleeding-through-libvips/, https://github.com/libvips/libvips/commit/00622428bda8d7521db8d74260b519fa41d69d0a, https://github.com/libvips/libvips/releases/tag/v8.7.4