🚨 [security] Update sqlite3: 5.0.0 → 5.0.6 (patch)
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ sqlite3 (5.0.0 → 5.0.6) · Repo · Changelog
Security Advisories 🚨
🚨 Denial-of-Service due to fatal error when binding invalid parameters
Impact
Affected versions 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
sqlite3v5.0.0, v5.0.1 and v5.0.2 are affected by this.Patches
Fixed in v5.0.3. All users are recommended to upgrade to v5.0.3 or later.
Workarounds
- Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters.
References
- GitHub commit: TryGhost/node-sqlite3@593c9d4
- Reported via issues: TryGhost/node-sqlite3#1440 and TryGhost/node-sqlite3#1449
- Snyk: https://security.snyk.io/vuln/SNYK-JS-SQLITE3-2388645
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Release Notes
5.0.6
What's Changed
- Updated bundled SQLite to v3.38.3 by @daniellockyer in TryGhost/node-sqlite3#1593. This fixes an upstream bug in SQLite that was reported here: TryGhost/node-sqlite3#1589
- Added Node 18 to CI by @daniellockyer in TryGhost/node-sqlite3#1587
Full Changelog: TryGhost/node-sqlite3@v5.0.5...v5.0.6
5.0.5
What's Changed
- Fixed building on certain systems (TryGhost/node-sqlite3#1584) by @daniellockyer
- General repository maintenance by @daniellockyer
Thank you to everyone reporting issues with building
sqlite3or the prebuilt binaries🙂 If you encounter an problem, please search open and closed issues for existing reports or open a new issue with as much system information as possible.Full Changelog: TryGhost/node-sqlite3@v5.0.4...v5.0.5
5.0.4
What's Changed
- Added prebuilt Linux musl binaries - @daniellockyer
- Added prebuilt Linux ARM64 binaries - @daniellockyer
- Fixed older glibc compatibility - @daniellockyer
Full Changelog: TryGhost/node-sqlite3@v5.0.3...v5.0.4
5.0.3
What's Changed
- Updated bundled SQLite to v3.38.2 - @daniellockyer
- Enabled math functions in compiler options - @kewde
- Updated
node-gypto v8.x - @daniellockyer- Re-enabled Node-API v6 builds - @daniellockyer
- Fixed segfault of invalid toString() object by @kewde in TryGhost/node-sqlite3#1450
- Fixed building on MacOS Monterey 12.3 - @daniellockyer
- Replaced Python extraction script with JS by @xPaw in TryGhost/node-sqlite3#1570
- Switched prebuilt binary hosting to GitHub Releases - @daniellockyer
Known Problems
- TryGhost/node-sqlite3#1578 - the minimum glibc version for prebuilt binaries was bumped to 2.29. We hope to bring this back down within the next few releases but you will need to compile from source if your system ships with a lower version.
- Prebuilt binaries for Linux do not work on musl systems. This should be fixed with TryGhost/node-sqlite3@8b2cdd9 but you will need to compile from source to use v5.0.3.
Full Changelog: TryGhost/node-sqlite3@v5.0.2...v5.0.3
5.0.2
v5.0.2
- disable N-API v6
5.0.1
5.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu recreate
- Recreates this PR, overwriting any edits that you've made to it
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)
Codecov Report
Merging #19 (7edd277) into main (b67366c) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## main #19 +/- ##
=======================================
Coverage 92.19% 92.19%
=======================================
Files 26 26
Lines 487 487
Branches 106 120 +14
=======================================
Hits 449 449
Misses 38 38
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update a6f5e49...7edd277. Read the comment docs.
Closed in favor of #23.