CVE-2019-6976
Libvips vulnerability
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.
Affected products
Libvips. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Libvips runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/libvips/libvips/commit/00622428bda8d7521db8d74260b519fa41d69d0a · Patch
- blog.silentsignal.eu/2019/04/18/drop-by-drop-bleeding-through-libvips/ · Third Party Advisory
- github.com/libvips/libvips/releases/tag/v8.7.4 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-6976
- cve.org/CVERecord?id=CVE-2019-6976
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.