CVE-2024-5171: heap buffer overflow in libaom
Integer overflow in libaom internal function imgallochelper can lead to heap buffer overflow. This function can be reached via 3 callers:
Calling aomimgalloc() with a large value of the dw, dh, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aomimaget struct may be invalid. Calling aomimgwrap() with a large value of the dw, dh, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aomimaget struct may be invalid. Calling aomimgallocwithborder() with a large value of the dw, dh, align, sizealign, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aomimaget struct may be invalid.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/aomto a version that resolves this vulnerability.Fixed in 1.0.0.errata1-3+deb11u2Fixed in 3.6.0-1+deb12u1Fixed in 3.12.0-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-5171?
CVE-2024-5171 is classified as a high severity vulnerability due to its potential for a heap buffer overflow.
How do I fix CVE-2024-5171?
To fix CVE-2024-5171, update the aom package to version 3.8.2-2ubuntu0.1 or 3.9.0 depending on your distribution.
What products are affected by CVE-2024-5171?
CVE-2024-5171 affects aom package versions prior to 3.8.2-2ubuntu0.1 and any versions before 3.9.0 in the libaom library.
What is the nature of the vulnerability in CVE-2024-5171?
CVE-2024-5171 involves an integer overflow in the libaom internal function img_alloc_helper, which can lead to heap buffer overflow.
How can I determine if my software is vulnerable to CVE-2024-5171?
Check if your installed version of the aom package is lower than 3.8.2-2ubuntu0.1 for Ubuntu or lower than 3.9.0 for other distributions.