SQLite vulnerabilities

A NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and trunk builds before e807d4e3798efd53 allows an attacker to cause a denial of service by supplying a malformed changeset blob. The issue occurs when sqlite3changeset_apply_v3() processes a corrupt changeset and calls sqlite3_value_type() with a NULL pointer.

Heap-based buffer overflow vulnerability in the FTS5 extension of SQLite before version 3.53.2. An attacker can supply a crafted database, causing a crash or arbitrary code execution during FTS5 MATCH query processing.

SQLite before 3.53.2 contains an out-of-bounds read vulnerability in the FTS5 full-text search extension. An attacker can supply a crafted database with a malformed FTS5 leaf page containing an oversized term length, causing fts5LeafSeek() to read past the page buffer during an FTS5 MATCH query.

In SQLite 3.44.0 through 3.49.0 before 3.49.1, the concat_ws() SQL function can write memory beyond the end of a malloc-allocated buffer. If the separator argument is attacker-controlled and is a large string (e.g., 2MB or more), an integer overflow occurs when calculating the result buffer size, so malloc may not allocate enough memory.

A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.

A critical vulnerability was found in SQLite up to 3.43.0 in the sessionReadRecord function of ext/session/sqlite3session.c. The manipulation leads to a heap-based buffer overflow. Applying a patch is recommended.

An issue found in SQLite SQLite3 v.3.35.4 that allows a remote attacker to cause a denial of service via the appendvfs.c function.

SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE. This can lead to unauthorized file writes.

In SQLite 3.31.1, a potential null pointer dereference was found in the INTERSEC query processing. This could lead to program crashes or unexpected behavior.

A flaw was found in SQLite's SELECT query functionality (src/select.c). This flaw allows an attacker who is capable of running SQL queries locally on the SQLite database to cause a denial of service or possible code execution by triggering a use-after-free. The highest threat from this vulnerability is to system availability.

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.

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

A vulnerability in SQLite before version 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.

SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow in ext/fts3/fts3.c, related to the snippet feature. The vulnerability affects the FTS3 full-text search module.

SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c. The fault can cause program crashes when processing certain SQL expressions.

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

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

ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving embedded '\0' characters in filenames, leading to a memory-management error that can be detected by (for example) valgrind.

selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.

A vulnerability in SQLite up to version 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements.

SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c.

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.