# CVE-2019-8457: Memory corruption in SQLite > An out-of-bounds read in SQLite's rtree handling allows attackers to cause denial of service or disclose memory contents. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 May 2019 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2019-8457, AZL-38326, CLEANSTART-2026-SX98768, DEBIAN-CVE-2019-8457, GHSA-p4jx-5p2x-4pq7, ROOT-OS-DEBIAN-11-CVE-2019-8457, SUSE-SU-2019:14083-1, SUSE-SU-2019:1601-1, UBUNTU-CVE-2019-8457, USN-4004-1, USN-4004-2 ## What is CVE-2019-8457? CVE-2019-8457 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 30 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2019-8457? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `sqlite3` | SUSE:Enterprise Storage 4 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 3.7.6.3-1.4.7.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 3.7.6.3-1.4.7.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 3.8.10.2-9.9.1 | | `sqlite3` | SUSE:OpenStack Cloud 7 | All versions | 3.8.10.2-9.9.1 | Products: Canonical Ubuntu Linux, Fedoraproject Fedora, Opensuse Leap, Sqlite Sqlite. ## How do I fix CVE-2019-8457? Upgrade to a fixed version. ## Is CVE-2019-8457 being exploited? There is no known exploitation of CVE-2019-8457 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-8457 and fix it if it is affected. What it is: CVE-2019-8457 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 30 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-8457 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-8457/ (Markdown: https://insights.sbomify.com/CVE-2019-8457/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-8457 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-8457 - OSV: https://osv.dev/vulnerability/CVE-2019-8457 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-8457/ Summaries are generated and may contain mistakes; the official description above is the record.