CVE-2024-5171

published 5 Jun 2024 · updated 19 Feb 2026

heap buffer overflow in libaom

10.0CriticalCVSS 10.0EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.9.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
libaom>=1.0.0 <3.9.03.9.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-5171 severity on Zeptric[![CVE-2024-5171](https://zeptric.io/badge/cve/CVE-2024-5171.svg)](https://zeptric.io/cve/CVE-2024-5171)