# CVE-2024-5197: Integer overflow in libvpx > Integer overflows in libvpx image allocation functions can lead to invalid struct fields, potentially causing memory corruption or crashes. - **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:N/SC:L/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 3 Jun 2024 - **Updated:** 13 Feb 2025 - **Also known as:** ALSA-2024:9827, AZL-42958, AZL-42963, CLSA-2025-1755003990, CLSA-2026-1777973407, DEBIAN-CVE-2024-5197, DLA-3830-1, DSA-5722-1, GHSA-4h58-f788-v8pw, JLSEC-2026-377, MGASA-2024-0221, OESA-2024-1716, RHSA-2024:9827, RHSA-2025:14138, RHSA-2025:14139, RHSA-2025:14140, RLSA-2024:9827, UBUNTU-CVE-2024-5197, USN-6814-1, USN-7249-1, openSUSE-SU-2024:14100-1 ## What is CVE-2024-5197? CVE-2024-5197 is a medium-severity vulnerability in Debian Debian Linux, published on 3 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description There exists interger overflows in libvpx in versions prior to 1.14.1. Calling vpx_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 vpx_image_t struct may be invalid. Calling vpx_img_wrap() with a large value of the d_w, d_h, or stride_align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned vpx_image_t struct may be invalid. We recommend upgrading to version 1.14.1 or beyond Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2024-5197? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libvpx` | AlmaLinux:9 | All versions | 1.9.0-8.el9_5 | | `libvpx-devel` | AlmaLinux:9 | All versions | 1.9.0-8.el9_5 | | `libvpx` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.0-8.el9_5 | | `libvpx-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.0-8.el9_5 | | `libvpx-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.0-8.el9_5 | | `libvpx-utils-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.0-8.el9_5 | | `libvpx-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.9.0-8.el9_5 | | `libvpx-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.9.0-8.el9_5 | | `libvpx-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.9.0-8.el9_5 | | `libvpx-utils-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.9.0-8.el9_5 | | `libvpx` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.0-7.el9_0.2 | | `libvpx-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.0-7.el9_0.2 | | `libvpx-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.0-7.el9_0.2 | | `libvpx-utils-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.0-7.el9_0.2 | | `libvpx` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.0-7.el9_2.2 | | `libvpx-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.0-7.el9_2.2 | | `libvpx-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.0-7.el9_2.2 | | `libvpx-utils-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.0-7.el9_2.2 | | `libvpx` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-utils-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-debuginfo` | Red Hat:rhel_eus:9.4::crb | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-debugsource` | Red Hat:rhel_eus:9.4::crb | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-devel` | Red Hat:rhel_eus:9.4::crb | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx-utils-debuginfo` | Red Hat:rhel_eus:9.4::crb | All versions | 0:1.9.0-7.el9_4.2 | | `libvpx` | Rocky Linux:9 | All versions | 0:1.9.0-8.el9_5 | | `libvpx` | openSUSE:Tumbleweed | All versions | 1.14.1-1.1 | Products: Debian Debian Linux, Webmproject Libvpx. ## How do I fix CVE-2024-5197? Upgrade to a fixed version. ## Is CVE-2024-5197 being exploited? There is no known exploitation of CVE-2024-5197 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-5197 and fix it if it is affected. What it is: CVE-2024-5197 is a medium-severity vulnerability in Debian Debian Linux, published on 3 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-5197 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-5197/ (Markdown: https://insights.sbomify.com/CVE-2024-5197/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5197 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5197 - OSV: https://osv.dev/vulnerability/CVE-2024-5197 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-5197/ Summaries are generated and may contain mistakes; the official description above is the record.