Integer Truncation on SQLite
SQLite
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| SQLitePCLRaw.lib.e_sqlite3 NuGet |
| No fix yet |
| SQLitePCLRaw.lib.e_sqlite3.android NuGet |
| No fix yet |
| SQLitePCLRaw.lib.e_sqlite3.ios NuGet |
|
SQLite
| Product | Affected | Fixed in |
|---|---|---|
| SQLitePCLRaw.lib.e_sqlite3 NuGet |
| No fix yet |
| SQLitePCLRaw.lib.e_sqlite3.android NuGet |
| No fix yet |
| SQLitePCLRaw.lib.e_sqlite3.ios NuGet |
|
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
From the CVE record · Google
SQLite versions before 3.50.2 can allow the number of aggregate terms to exceed the number of available columns, potentially causing memory corruption. The input does not specify how an attacker could trigger this issue or whether network access, authentication, or user interaction is required.
Engineers running SQLite before 3.50.2 or NuGet packages SQLitePCLRaw.lib.e_sqlite3, SQLitePCLRaw.lib.e_sqlite3.android, or SQLitePCLRaw.lib.e_sqlite3.ios at version 2.1.11 or earlier should check their deployments.