| Name | CVE-2019-8457 |
| 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 929775, 1010974 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| db5.3 (PTS) | bullseye | 5.3.28+dfsg1-0.8 | vulnerable |
| bookworm | 5.3.28+dfsg2-1 | fixed |
| sid, trixie | 5.3.28+dfsg2-9 | fixed |
| sqlite3 (PTS) | bullseye | 3.34.1-3 | fixed |
| bullseye (security) | 3.34.1-3+deb11u1 | fixed |
| bookworm | 3.40.1-2+deb12u1 | fixed |
| sid, trixie | 3.46.1-6 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| db5.3 | source | (unstable) | 5.3.28+dfsg1-0.9 | | | 1010974 |
| sqlite | source | (unstable) | (not affected) | | | |
| sqlite3 | source | (unstable) | 3.27.2-3 | | | 929775 |
Notes
[bullseye] - db5.3 <ignored> (vulnerable code is present but unused in Debian, and fix is too risky to backport)
[buster] - db5.3 <ignored> (vulnerable code is present but unused in Debian, and fix is too risky to backport)
[stretch] - db5.3 <ignored> (vulnerable code is present but unused in Debian, and fix is too risky to backport)
[stretch] - sqlite3 <ignored> (vulnerable code is present but unused in Debian, and fix is too risky to backport)
[jessie] - sqlite3 <ignored> (vulnerable code is present but unused in Debian, and fix is too risky to backport)
- sqlite <not-affected> (rtree extension not present in v2)
Fixed by: https://www.sqlite.org/src/info/90acdbfce9c08858
Make the internal dynamic string interface available to extensions:
https://sqlite.org/src/info/87f261f0cb800b06
Affected function is not used in Debian and meant for debugging purposes,
backporting the fix would be very complex.
https://lists.debian.org/debian-lts/2023/06/msg00012.html
https://lists.debian.org/debian-lts/2019/06/msg00013.html
https://lists.debian.org/debian-lts/2019/06/msg00036.html