There exists interger overflows in libvpx in versions prior to 1.14.1. Calling vpx_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned vpx_image_t struct may be invalid. Calling vpx_img_wrap() with a large value of the d_w, d_h, or stride_align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned vpx_image_t struct may be invalid. We recommend upgrading to version 1.14.1 or beyond
Existen desbordamientos de enteros en libvpx en versiones anteriores a la 1.14.1. Llamar a vpx_img_alloc() con un valor grande del parámetro d_w, d_h o align puede provocar desbordamientos de enteros en los cálculos de tamaños y compensaciones del búfer y algunos campos de la estructura vpx_image_t devuelta pueden no ser válidos. Llamar a vpx_img_wrap() con un valor grande del parámetro d_w, d_h o stride_align puede provocar desbordamientos de enteros en los cálculos de tamaños y compensaciones del búfer y algunos campos de la estructura vpx_image_t devuelta pueden no ser válidos. Recomendamos actualizar a la versión 1.14.1 o posterior
A flaw was found in libvpx. When creating images, libvpx trusts the width, height, and alignment of the user input. However, it does not properly validate the provided values. This flaw allows an attacker to craft user inputs or trick the user into opening crafted files, where these types of values are invalid, leading to integer overflows during memory allocation procedures. A successful full attack leads to the targeted application crashing, resulting in a denial of service or memory corruption, which results in data integrity issues.
