p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de sqlite3

Vulnérabilité publiée pour sqlite3 au cours des 30 derniers jours : 1. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 5

  1. CVE-2026-128084

    Moyenne · CVSS 4.8EPSS 0,31%Correctif disponible

    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 Database#prepare, bound String or Blob values through Statement#bind_param, and String or Blob results from Ruby-defined SQL functions and aggregates through Database#create_function and Database#create_aggregate. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger can wrap the length so SQLite processes only a prefix. A truncated SQL string can drop trailing clauses such as a WHERE condition, while a truncated bound value matters only when the application validated the full valu

    • Mettez à jour vers 2.10.2
    Publication Mise à jour
  2. GHSA-mwm8-39rw-8826

    Moyenne · CVSS 6.3Correctif disponible

    sqlite3-ruby: Use-After-Free in SQLite Aggregate Arguments in Heap-Allocated Argument Array

    ## Summary Using `Database#create_aggregate`, `#create_aggregate_handler`, or `Database#define_aggregator` 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 being converted, during ordinary garbage collection. The aggregate's `step` method then receives an incorrect object, or the process crashes with a segmentation fault. ## Mitigation Upgrade to sqlite3 gem v2.9.6 or later. There is no reliable workaround. If you cannot upgrade, avoid defining aggregate functions that take two or more

    • Mettez à jour vers 2.9.6
    Publication Mise à jour
  3. CVE-2026-54620

    Faible · CVSS 2EPSS 0,14%Correctif disponible

    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.

    • Mettez à jour vers 2.9.5
    Publication Mise à jour
  4. CVE-2026-54619

    Faible · CVSS 2EPSS 0,14%Correctif disponible

    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 2.9.5.

    • Mettez à jour vers 2.9.5
    Publication Mise à jour
  5. GHSA-mgvv-5mxp-xq67

    Non évaluéeCorrectif disponible

    SQLite3 addresses vulnerability in packaged version of libsqlite

    ### Summary The rubygem sqlite3 v1.5.1 upgrades the packaged version of libsqlite from v3.39.3 to [v3.39.4](https://sqlite.org/releaselog/3_39_4.html). libsqlite v3.39.4 addresses a vulnerability described as follows in the release notification: > Version 3.39.4 is a minimal patch against the prior release that addresses issues found since the > prior release. In particular, a potential vulnerability in the FTS3 extension has been fixed, so > this should be considered a security update. > > In order to exploit the vulnerability, an attacker must have full SQL access and must be able to > construct a corrupt database with over 2GB of FTS3 c

    • Mettez à jour vers 1.5.1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →