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.
History

Sat, 07 Sep 2024 22:30:00 +0000

Type Values Removed Values Added
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Google

Published: 2024-06-05T19:11:12.987Z

Updated: 2024-09-07T21:02:30.315Z

Reserved: 2024-05-21T12:53:59.515Z

Link: CVE-2024-5171

cve-icon Vulnrichment

Updated: 2024-09-07T21:02:30.315Z

cve-icon NVD

Status : Modified

Published: 2024-06-05T20:15:13.800

Modified: 2024-11-21T09:47:07.493

Link: CVE-2024-5171

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-06-05T00:00:00Z

Links: CVE-2024-5171 - Bugzilla