/ 
DBD-SQLite-1.36_03
River stage four • 571 direct dependents • 1574 total dependents
⭐ Starred 28 GitHub stars
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.36_03

  • Updated to SQLite 3.7.11 (ISHIGAKI)
  • Fix >32bit integer truncation and other sqlite_set_result condition issue (Yuriy Kaminskiy)
  • Fix integer overflow in passing argument to perl function (Yuriy Kaminskiy)
  • Convert unsigned -> int64 when possible (Yuriy Kaminskiy)
  • Turned datatype mismatch error (introduced in 1.34_02) into a warning (you can disable this warning by setting PrintWarn attribute to false). (ISHIGAKI)
  • Refactored sqlite_is_number to fix various corner cases (ISHIGAKI)

Changes for version 1.36_02

  • Downgraded SQLite to 3.7.9, as 3.7.10 turned out to be broken on the latest MacOS X (due to a missing symbol), and broke other modules that typically use temporary tables under a few environments too. As of this writing, would-be 3.7.11 seems fine, but it would take another month to be released. (ISHIGAKI)

Changes for version 1.36_01

  • CHANGES THAT MAY POSSIBLY BREAK YOUR OLD APPLICATIONS ***
  • Updated to SQLite 3.7.10 (ISHIGAKI) Note that this release changed the default schema format number, that means newly created database files will be unreadable by SQLite version prior to 3.3.0 (2006-01-10) (or DBD::SQLite prior to 1.12) unless you explicitly issue "PRAGMA legacy_file_format=ON".
  • Enabled SQLITE_ENABLE_FTS4
  • Enabled SQLITE_ENABLE_STAT3
  • Resolved #73159: FTS tokenizer segfault (ISHIGAKI)
  • Resolved #73787: sqlite_see_if_its_a_number causes a buffer overflow (ISHIGAKI)
  • Resolved #73314 for DBD-SQLite: binding of 64bit integers fail on 1.34_02 (ISHIGAKI)
  • Implemented sqlite_trace and sqlite_profile methods for simpler tracing/profiling; use DBI_TRACE/DBI_PROFILE for more complicated cases (ISHIGAKI)

Documentation

DBD::SQLite::Cookbook
The DBD::SQLite Cookbook

Modules

DBD::SQLite
Self-contained RDBMS in a DBI Driver

Provides

DBD::SQLite::_WriteOnceHash
in lib/DBD/SQLite.pm
DBD::SQLite::db
in lib/DBD/SQLite.pm
DBD::SQLite::dr
in lib/DBD/SQLite.pm

Other files