| Name | CVE-2019-19244 |
| Description | sqlite3Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | ELA-1191-1 |
| Debian Bugs | 946656 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| sqlite (PTS) | jessie, jessie (lts) | 2.8.17-12+deb8u1 | fixed |
| stretch (lts), stretch | 2.8.17-14+deb9u1 | fixed |
| buster (security), buster, buster (lts) | 2.8.17-15+deb10u1 | fixed |
| sqlite3 (PTS) | jessie, jessie (lts) | 3.8.7.1-1+deb8u8 | fixed |
| stretch (security) | 3.16.2-5+deb9u3 | fixed |
| stretch (lts), stretch | 3.16.2-5+deb9u4 | fixed |
| buster, buster (lts) | 3.27.2-3+deb10u3 | fixed |
| buster (security) | 3.27.2-3+deb10u2 | vulnerable |
| 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-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| sqlite | source | (unstable) | (not affected) | | | |
| sqlite3 | source | wheezy | (not affected) | | | |
| sqlite3 | source | jessie | (not affected) | | | |
| sqlite3 | source | stretch | (not affected) | | | |
| sqlite3 | source | buster | 3.27.2-3+deb10u3 | | ELA-1191-1 | |
| sqlite3 | source | (unstable) | 3.30.1+fossil191229-1 | unimportant | | 946656 |
Notes
[stretch] - sqlite3 <not-affected> (Vulnerable code introduced later)
[jessie] - sqlite3 <not-affected> (Vulnerable code, i.e. window functions, not present)
- sqlite <not-affected> (Vulnerable code, i.e. window functions, not present)
https://github.com/sqlite/sqlite/commit/e59c562b3f6894f84c715772c4b116d7b5c01348
CLI crash is only triggerable with SQLITE_DEBUG builds by reaching an asserion statement
in sqlite3VdbeExec function. Debian does not use SQLITE_DEBUG for the regular builds.
In non-debug builds this results in wrong output/result from the query only.
https://bugzilla.redhat.com/show_bug.cgi?id=1777945#c3
[wheezy] - sqlite3 <not-affected> (Vulnerable code not present)