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.
References
Link | Resource |
---|---|
https://github.com/libvips/libvips/releases/tag/v8.7.4 | Third Party Advisory |
https://github.com/libvips/libvips/commit/00622428bda8d7521db8d74260b519fa41d69d0a | Patch Third Party Advisory |
https://blog.silentsignal.eu/2019/04/18/drop-by-drop-bleeding-through-libvips/ | Technical Description Third Party Advisory |
Configurations
Information
Published : 2019-01-26 15:29
Updated : 2020-08-24 10:37
NVD link : CVE-2019-6976
Mitre link : CVE-2019-6976
JSON object : View
CWE
CWE-908
Use of Uninitialized Resource
Products Affected
libvips_project
- libvips