Security Advisories (20)
CVE-2020-13434 (2020-05-24)

SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

CVE-2020-11656 (2020-04-09)

In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compound SELECT statement.

CVE-2020-9327 (2020-02-21)

In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and segmentation fault because of generated column optimizations.

CVE-2018-20506 (2019-04-03)

SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries in a "merge" operation that occurs after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases). This is a different vulnerability than CVE-2018-20346.

CVE-2015-3416 (2015-04-24)

The sqlite3VXPrintf function in printf.c in SQLite before 3.8.9 does not properly handle precision and width values during floating-point conversions, which allows context-dependent attackers to cause a denial of service (integer overflow and stack-based buffer overflow) or possibly have unspecified other impact via large integers in a crafted printf function call in a SELECT statement.

CVE-2015-3414 (2015-04-24)

SQLite before 3.8.9 does not properly implement the dequoting of collation-sequence names, which allows context-dependent attackers to cause a denial of service (uninitialized memory access and application crash) or possibly have unspecified other impact via a crafted COLLATE clause, as demonstrated by COLLATE"""""""" at the end of a SELECT statement.

CVE-2020-13630 (2020-05-27)

ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

CVE-2019-8457 (2019-05-30)

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.

CVE-2020-15358 (2020-06-27)

In SQLite before 3.32.3, select.c mishandles query-flattener optimization, leading to a multiSelectOrderBy heap overflow because of misuse of transitive properties for constant propagation.

CVE-2020-13632 (2020-05-27)

ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.

CVE-2020-13631 (2020-05-27)

SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.

CVE-2020-13435 (2020-05-24)

SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c.

CVE-2020-11655 (2020-04-09)

SQLite through 3.31.1 allows attackers to cause a denial of service (segmentation fault) via a malformed window-function query because the AggInfo object's initialization is mishandled.

CVE-2019-19646 (2019-12-09)

pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns.

CVE-2019-19645 (2019-12-09)

alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements.

CVE-2018-20346 (2018-12-21)

SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries that occur after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases), aka Magellan.

CVE-2018-8740 (2018-03-17)

In SQLite through 3.22.0, databases whose schema is corrupted using a CREATE TABLE AS statement could cause a NULL pointer dereference, related to build.c and prepare.c.

CVE-2017-10989 (2017-07-07)

The getNodeSize function in ext/rtree/rtree.c in SQLite through 3.19.3, as used in GDAL and other products, mishandles undersized RTree blobs in a crafted database, leading to a heap-based buffer over-read or possibly unspecified other impact.

CVE-2015-3415 (2015-04-24)

The sqlite3VdbeExec function in vdbe.c in SQLite before 3.8.9 does not properly implement comparison operators, which allows context-dependent attackers to cause a denial of service (invalid free operation) or possibly have unspecified other impact via a crafted CHECK clause, as demonstrated by CHECK(0&O>O) in a CREATE TABLE statement.

CVE-2016-6153 (2016-09-26)

os_unix.c in SQLite before 3.13.0 improperly implements the temporary directory search algorithm, which might allow local users to obtain sensitive information, cause a denial of service (application crash), or have unspecified other impact by leveraging use of the current working directory for temporary files.

Changes for version 1.39

  • Production release, no changes from 1.38_05

Changes for version 1.38_05

  • OpenBSD doesn't like the previous _XOPEN_SOURCE hack (ISHIGAKI)
  • Disabled a unicode-related test for older perls (ISHIGAKI)

Changes for version 1.38_04

  • Tentatively defined _XOPEN_SOURCE under *BSD systems to see if it solves a compilation issue for threaded perls (ISHIGAKI)

Changes for version 1.38_03

  • NOTICE ON QUERY OPTIMIZER ENHANCEMENT ***
  • As of SQLite 3.7.15, SQLite's query optimizer was enhanced and the result order of a SELECT statement without an ORDER BY clause may be different from the one of the previous versions. If your applications or tests mistakenly depend on the arbitrary output order, they may be broken with this enhancement.
  • Updated to SQLite 3.7.17 (ISHIGAKI)
  • Fixed tests that mistakenly made invalid assumptions about the result order (ISHIGAKI)
  • Added a brief note on useful pragmata. (ISHIGAKI)
  • Resolved #85302: type fixes (ISHIGAKI)

Changes for version 1.38_02

  • Updated to SQLite 3.7.16.1 (ISHIGAKI)
  • Removed two obsolete pragma calls at login time (ISHIGAKI)
  • Resolved #80344: Set SQLITE_DISABLE_DIRSYNC on AIX (suggested by Steve Barnsley) (ISHIGAKI)
  • Resolved #81536: primary_key_info returns the wrong KEY_SEQ (VLYON)
  • Resolved #84027: Finalizer() not called in (D. Richard Hipp)
  • Resolved #84372: -Wpointer-sign warnings with utf8_hop (RURBAN)
  • Resolved #84373: Add test for RT #26775 "name)" key with DISTINCT (RURBAN/ISHIGAKI)
  • Resolved #70815: DBD::SQLite 1.33 build is broken under Solaris using Sun C (RURBAN)
  • Resolved #84380: Fix WINLIKE for mingw/msys (RURBAN)
  • Added a note on DBD::SQLite and File::Temp (suggested by TOKUHIROM) (ISHIGAKI)

Changes for version 1.38_01

  • CHANGES THAT MAY POSSIBLY BREAK YOUR OLD APPLICATIONS ***
  • Resolved #56444: immediate transaction should be on by default, and the doc be updated. If you really need the deferred transaction (which had long been the default), set sqlite_use_immediate_transaction to false explicitly. (ISHIGAKI)
  • Updated to SQLite 3.7.14 (ISHIGAKI)
  • Added support for foreign_key_info (DAMI/ISHIGAKI)
  • Added several methods to retrieve internal information such as table_column_metadata/db_filename/*_status (ISHIGAKI/VOVKASM)
  • Added sqlite_load_extension so that extensions can add functions internally (ISHIGAKI)
  • Resolved #77617: atoll () sometimes just is atol () (GAAS)
  • Resolved #48084: improper "require utf8" in tests (ISHIGAKI)
  • Resolved #77724: bug in primary_key_info with regard to column names containing whitespace (ISHIGAKI)
  • Resolved #79364: variance example of the doc (ISHIGAKI)
  • Resolved #78833: utf8 flag for column names (JAMADAM) (This hopefully resolved #72418 as well)
  • Resolved #64177: ping() wipes out the errstr (ISHIGAKI)
  • Resolved #79576: (patch) bind_param don't work with PADTMP scalars (VOVKASM)
  • Refactored primary_key_info to support attached databases (ISHIGAKI)

Documentation

The DBD::SQLite Cookbook

Modules

Self-contained RDBMS in a DBI Driver

Provides

in lib/DBD/SQLite.pm
in lib/DBD/SQLite.pm
in lib/DBD/SQLite.pm