31 matches found
sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger
Summary sqlite3-ruby cast Ruby string lengths long to int before passing them to SQLite. On 64-bit platforms, a string of 4 GiB 2^32 bytes or larger had its length wrap, so SQLite saw only the first length mod 2^32 bytes. An attacker who controls the length of a SQL string could truncate the quer...
GHSA-4FQR-96Q8-XRFX sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger
Summary sqlite3-ruby cast Ruby string lengths long to int before passing them to SQLite. On 64-bit platforms, a string of 4 GiB 2^32 bytes or larger had its length wrap, so SQLite saw only the first length mod 2^32 bytes. An attacker who controls the length of a SQL string could truncate the quer...
CVE-2026-128084
The sqlite3-ruby library is vulnerable to SQL query truncation on 64-bit platforms because it casts Ruby string lengths (long) to integers before passing them to SQLite. Strings of 4 GiB (2^32 bytes) or larger cause the length to wrap, leading SQLite to process only a prefix. This can result in d...
CVE-2026-128084 sqlite3-ruby: SQL Query Truncation
sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Databaseprepare, bound String or Blob values through Statementbindparam, and String or Blob results from Ruby-defined SQL functions and...
EUVD-2026-125713
sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Databaseprepare, bound String or Blob values through Statementbindparam, and String or Blob results from Ruby-defined SQL functions and...
CVE-2026-128084 sqlite3-ruby: SQL Query Truncation
sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Databaseprepare, bound String or Blob values through Statementbindparam, and String or Blob results from Ruby-defined SQL functions and...
GHSA-MWM8-39RW-8826 sqlite3-ruby: Use-After-Free in SQLite Aggregate Arguments in Heap-Allocated Argument Array
Summary Using Databasecreateaggregate, createaggregatehandler, or Databasedefineaggregator to define an aggregate function that takes two or more arguments, and then evaluating it over TEXT or BLOB column values, can free the Ruby objects holding those arguments while a later argument is still...
sqlite3-ruby: Use-After-Free in SQLite Aggregate Arguments in Heap-Allocated Argument Array
Summary Using Databasecreateaggregate, createaggregatehandler, or Databasedefineaggregator to define an aggregate function that takes two or more arguments, and then evaluating it over TEXT or BLOB column values, can free the Ruby objects holding those arguments while a later argument is still...
Use After Free
Overview Affected versions of this package are vulnerable to Use After Free in rbsqlite3aggregatorstep in ext/sqlite3/aggregator.c. An attacker can make the aggregate step method receive a wrong or freed Ruby object, or crash the process, by invoking a multi-argument aggregate over...
SUSE CVE-2026-54619
sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version...
CVE-2026-54619
A flaw was found in sqlite3-ruby. When a SQLite function is redefined with a different number of arguments arity, the previously registered function handler is prematurely freed. This can lead to a use-after-free vulnerability, where the program attempts to access memory that has already been...
CVE-2026-54620
A flaw was found in sqlite3-ruby, a Ruby binding for the SQLite3 embedded database. This vulnerability occurs because callbacks used for SQLite aggregate functions can be prematurely freed while still being referenced during aggregation. A local attacker could potentially exploit this...
CVE-2026-54620 sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks
sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5...
CVE-2026-54620
sqlite3-ruby (Ruby bindings for SQLite3) is affected by a Use-After-Free in aggregate function callbacks. From versions 2.1.0 through 2.9.4, callbacks for aggregate functions can be freed while still referenced during aggregation, causing an invalid memory read or a segmentation fault. The issue ...
CVE-2026-54620 sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks
sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5...
CVE-2026-54620 sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks
sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5...
GHSA-28HH-PR2H-2W89 sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
Summary Using Databasecreatefunction or Databasedefinefunction to define the same function name more than once with different numbers of arguments "arity" or text encodings will result in a invalid memory read and a segmentation fault. Mitigation Upgrade to sqlite3 gem v2.9.5 or later. As a...
CVE-2026-54619 sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version...
CVE-2026-54619 sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version...