Skip to content

← Public intelligence

npm package

sqlite3

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.1npmAmendedPublished

    sqlite vulnerable to code execution due to Object coercion

    CVE-2022-43441 · GHSA-jqv5-7xpx-qj74

    Affected
    • npm sqlite3 >= 5.0.0, < 5.1.5
    Fixed in
    5.1.5· Vendor fix available
    Issue
    Impact Due to the underlying implementation of .ToString(), it's possible to execute arbitrary JavaScript, or to achieve a denial-of-service, if a binding parameter is a crafted Object. Users of sqlite3 v5.0.0 - v5.1.4 are affected by this. Patches Fixed in v5.1.5. All users are recommended to upgrade to v5.1.5 or later. Workarounds Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters. References Commit: https://github.com/TryGhost/node-sqlite3/commit/edb1934dd222ae55632e120d8f64552d5191c781 For more information If you have any questions or comments about this advisory: Email us at security@ghost.org Credits: Dave McDaniel of Cisco Talos

    Recommended action: Upgrade to 5.1.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 7.5npmAmendedPublished

    Denial-of-Service when binding invalid parameters in sqlite3

    CVE-2022-21227 · GHSA-9qrh-qjmc-5w2p

    Affected
    • npm sqlite3 >= 5.0.0, < 5.0.3
    Fixed in
    5.0.3· Vendor fix available
    Issue
    Affected versions of sqlite3 will experience a fatal error when supplying a specific object in the parameter array. This error causes the application to crash and could not be caught. Users of sqlite3 v5.0.0, v5.0.1 and v5.0.2 are affected by this. This issue is fixed in v5.0.3. All users are recommended to upgrade to v5.0.3 or later. Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters as a workaround.

    Recommended action: Upgrade to 5.0.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →