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.
{
"binaries": [
{
"binary_version": "8.2.2-1ubuntu0.1~esm1",
"binary_name": "gir1.2-vips-8.0"
},
{
"binary_version": "8.2.2-1ubuntu0.1~esm1",
"binary_name": "libvips-dev"
},
{
"binary_version": "8.2.2-1ubuntu0.1~esm1",
"binary_name": "libvips-tools"
},
{
"binary_version": "8.2.2-1ubuntu0.1~esm1",
"binary_name": "libvips42"
},
{
"binary_version": "8.2.2-1ubuntu0.1~esm1",
"binary_name": "python-vipscc"
}
],
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro"
}
{
"binaries": [
{
"binary_version": "8.4.5-1ubuntu0.1~esm1",
"binary_name": "gir1.2-vips-8.0"
},
{
"binary_version": "8.4.5-1ubuntu0.1~esm1",
"binary_name": "libvips-dev"
},
{
"binary_version": "8.4.5-1ubuntu0.1~esm1",
"binary_name": "libvips-tools"
},
{
"binary_version": "8.4.5-1ubuntu0.1~esm1",
"binary_name": "libvips42"
},
{
"binary_version": "8.4.5-1ubuntu0.1~esm1",
"binary_name": "python-vipscc"
}
],
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro"
}