First published: Tue Jun 04 2024(Updated: )
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.
Credit: cve-coordination@google.com cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
ubuntu/aom | <3.8.2-2ubuntu0.1 | 3.8.2-2ubuntu0.1 |
ubuntu/aom | <3.9.0 | 3.9.0 |
Aomedia Libaom | >=1.0.0<=3.9.0 | |
debian/aom | <=1.0.0.errata1-3+deb11u1<=3.6.0-1 | 3.6.0-1+deb12u1 3.9.1-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.