Resolution
As of OpenUSD 25.08, libaom has been upgraded to 3.12.1 (see commit 7a31d7e).
Summary
The plugin hioAvif embeds libaom which is based on version 3.8.3. libaom 3.8.3 has a known critical vulnerability (CVE-2024-5171) which has been fixed in libaom 3.10.0
Details
Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_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 aom_image_t struct may be invalid. * Calling aom_img_wrap() 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 aom_image_t struct may be invalid. * Calling aom_img_alloc_with_border() with a large value of the d_w, d_h, align, size_align, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid.
PoC
No PoC is provided as the vulnerability is already fixed in libaom 3.10.0
Impact
Resolution
As of OpenUSD 25.08, libaom has been upgraded to 3.12.1 (see commit 7a31d7e).
Summary
The plugin hioAvif embeds libaom which is based on version 3.8.3. libaom 3.8.3 has a known critical vulnerability (CVE-2024-5171) which has been fixed in libaom 3.10.0
Details
Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_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 aom_image_t struct may be invalid. * Calling aom_img_wrap() 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 aom_image_t struct may be invalid. * Calling aom_img_alloc_with_border() with a large value of the d_w, d_h, align, size_align, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid.
PoC
No PoC is provided as the vulnerability is already fixed in libaom 3.10.0
Impact