Skip to content

🔒 [Security Fix] Use cryptographically secure randomness for savepoint names - #449

Merged
zknpr merged 1 commit into
mainfrom
fix-insecure-randomness-savepoints-17206054167106175443
Jun 8, 2026
Merged

🔒 [Security Fix] Use cryptographically secure randomness for savepoint names#449
zknpr merged 1 commit into
mainfrom
fix-insecure-randomness-savepoints-17206054167106175443

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor
  • 🎯 What: The vulnerability fixed was the use of Math.random() to generate savepoint names in WasmDatabaseEngine.
  • ⚠️ Risk: The potential impact if left unfixed is that Math.random() generates predictable values, allowing an attacker to guess savepoint names, potentially leading to unauthorized data manipulation or race conditions when savepoints are released or rolled back prematurely in nested transactions.
  • 🛡️ Solution: How the fix addresses the vulnerability by replacing Math.random() with crypto.randomUUID() from cryptoShim and ensuring consistent savepoint name generation via the createSavepointName method.

PR created automatically by Jules for task 17206054167106175443 started by @zknpr

Replaces Math.random() with crypto.randomUUID() via cryptoShim to ensure unique and secure savepoint name generation. Refactors inline savepoint logic to reuse createSavepointName.
@google-labs-jules

Copy link
Copy Markdown
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel

vercel Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sq-lite-explorer Ready Ready Preview, Comment Jun 8, 2026 12:27pm

@zknpr
zknpr merged commit f418365 into main Jun 8, 2026
6 checks passed
@zknpr
zknpr deleted the fix-insecure-randomness-savepoints-17206054167106175443 branch June 8, 2026 16:33
zknpr added a commit that referenced this pull request Jun 14, 2026
The first draft only listed this session's PRs (#457+). main had ~20 more
unreleased PRs merged after the v1.5.2 tag (#428#456) that were never
changelogged — fixes (#456 rowid validation, #453 data masking), a security
fix (#449 crypto savepoint names), perf (#443, #439, #440), refactors, tests,
and dep bumps. Entry now reflects the full v1.5.2..HEAD range.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
zknpr added a commit that referenced this pull request Jun 14, 2026
* chore: release 1.5.3

Maintenance release covering everything merged since 1.5.2: internal
code-health, expanded unit-test coverage, and dev-dependency bumps. No
user-facing behavior change; error logging now routes to the SQLite
Explorer output channel.

package.json version + CHANGELOG only — package-lock.json left at 1.5.2
per the project's lockfile-drift convention.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs(changelog): expand 1.5.3 to cover all PRs since v1.5.2

The first draft only listed this session's PRs (#457+). main had ~20 more
unreleased PRs merged after the v1.5.2 tag (#428#456) that were never
changelogged — fixes (#456 rowid validation, #453 data masking), a security
fix (#449 crypto savepoint names), perf (#443, #439, #440), refactors, tests,
and dep bumps. Entry now reflects the full v1.5.2..HEAD range.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant