In the library developed by the Open Media Alliance (AOMedia) libaomwhich provides a reference implementation of the AV1 video encoding format, a critical vulnerability (CVE-2024-5171), leading to integer overflow and out-of-bounds writes when processing too large values in some parameters. Similar vulnerability (CVE-2024-5197) identified in the library libvpx with the implementation of VP8 and VP9 codecs. Problems fixed in updates libaom 3.9.0 And libvpx 1.14.1. In distribution kits, vulnerabilities still remain uncorrected (Debian, Ubuntu, RHEL, SUSE/openSUSE, Fedora, Arch, FreeBSD).
Vulnerabilities in libaom assigned maximum level of danger (10 out of 10), implying the possibility of exploitation when processing specially designed content in applications using this library. In libvpx the danger level exhibited 5.9 out of 10, which corresponds to limited operating conditions. The main danger of vulnerabilities in libaom and libvpx is caused by the fact that these libraries are used in web browsers, media players and services that transcode video.
The vulnerability occurs in libaom when calling the aom_img_alloc(), aom_img_wrap() or om_img_alloc_with_border() functions with large values in the d_w, d_h and align parameters, which lead to an integer overflow when calculating offsets and buffer sizes. A similar overflow occurs in the vpx_img_alloc() and vpx_img_wrap() functions. These functions are used when encoding video.
The vulnerability is most dangerous due to the potential for attacks on browsers in which past similar vulnerabilities could be exploited by opening a specially designed page in the browser that calls JavaScript functions for video encoding, or through manipulation of WebRTC. By statement Google representatives, the vulnerability does not affect the Chromium engine, since only verified values of the d_w and d_h arguments were passed to the aom_img_alloc(), aom_img_wrap(), vpx_img_alloc() and vpx_img_wrap() functions. Firefox uses a library to decode AV1 dav1dbut for coding applies libaom. It is not yet clear whether Firefox is affected by the problem, as information about how the vulnerability affects specific products has not yet been published.
Thanks for reading: