# CVE-2019-13616: Memory corruption in n/a > A heap-based buffer over-read in the SDL library allows attackers to cause denial of service or disclose sensitive memory contents. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 16 Jul 2019 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2019-13616, DEBIAN-CVE-2019-13616, GHSA-v89f-grvw-gpv8, MGASA-2019-0254, RHSA-2019:3950, RHSA-2019:3951, RHSA-2020:0293, SUSE-SU-2020:3030-1, SUSE-SU-2020:3261-1, UBUNTU-CVE-2019-13616, openSUSE-SU-2020:1916-1, openSUSE-SU-2020:1990-1 ## What is CVE-2019-13616? CVE-2019-13616 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 16 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer over-read in BlitNtoN in video/SDL_blit_N.c when called from SDL_SoftBlit in video/SDL_blit.c. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2019-13616? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `SDL` | Red Hat:enterprise_linux:7::client | All versions | 0:1.2.15-14.el7_7 | | `SDL-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.2.15-14.el7_7 | | `SDL-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.2.15-14.el7_7 | | `SDL-static` | Red Hat:enterprise_linux:7::client | All versions | 0:1.2.15-14.el7_7 | | `SDL` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.2.15-14.el7_7 | | `SDL-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.2.15-14.el7_7 | | `SDL-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.2.15-14.el7_7 | | `SDL-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.2.15-14.el7_7 | | `SDL` | Red Hat:enterprise_linux:7::server | All versions | 0:1.2.15-14.el7_7 | | `SDL-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.2.15-14.el7_7 | | `SDL-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.2.15-14.el7_7 | | `SDL-static` | Red Hat:enterprise_linux:7::server | All versions | 0:1.2.15-14.el7_7 | | `SDL` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.2.15-14.el7_7 | | `SDL-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.2.15-14.el7_7 | | `SDL-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.2.15-14.el7_7 | | `SDL-static` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.2.15-14.el7_7 | | `SDL` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.15-36.el8_1 | | `SDL-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.15-36.el8_1 | | `SDL-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.15-36.el8_1 | | `SDL-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.15-36.el8_1 | | `SDL` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:1.2.15-33.el8_0 | | `SDL-debuginfo` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:1.2.15-33.el8_0 | | `SDL-debugsource` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:1.2.15-33.el8_0 | | `SDL-devel` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:1.2.15-33.el8_0 | | `SDL` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 1.2.15-3.12.73 | | `SDL` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP2 | All versions | 1.2.15-3.12.73 | | `SDL` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.2.15-15.14.2 | | `SDL` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.2.15-15.14.2 | | `SDL` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.2.15-15.14.2 | | `SDL` | openSUSE:Leap 15.1 | All versions | 1.2.15-lp151.4.3.1 | | `SDL` | openSUSE:Leap 15.2 | All versions | 1.2.15-lp152.5.3.1 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Libsdl Simple Directmedia Layer, Opensuse Backports Sle, Opensuse Leap, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation. ## How do I fix CVE-2019-13616? Upgrade to a fixed version. ## Is CVE-2019-13616 being exploited? There is no known exploitation of CVE-2019-13616 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-13616 and fix it if it is affected. What it is: CVE-2019-13616 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 16 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-13616 in the wild and no public exploit code. Affected product: Canonical Ubuntu 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-2019-13616/ (Markdown: https://insights.sbomify.com/CVE-2019-13616/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13616 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13616 - OSV: https://osv.dev/vulnerability/CVE-2019-13616 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-13616/ Summaries are generated and may contain mistakes; the official description above is the record.