Skip to content

πŸ›‘οΈ Sentinel: sanitize sensitive data in error reporting - #133

Draft
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
sentinel/redact-sensitive-error-context-15838035201127298316
Draft

πŸ›‘οΈ Sentinel: sanitize sensitive data in error reporting#133
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
sentinel/redact-sensitive-error-context-15838035201127298316

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor

🚨 Severity

MEDIUM

πŸ’‘ Vulnerability

Un-sanitized error objects and error context passed into reportError could inadvertently write sensitive user or system data (such as API keys, passwords, bearer tokens, or Vercel Blob read/write tokens) into console logs or external monitoring aggregators.

🎯 Impact

If credentials or tokens appear in exception messages or context payloads, they could be leaked to log management platforms, third-party log ingestion tools, or client browser consoles.

πŸ”§ Fix

Added recursive data sanitization to app/lib/error-reporting.ts:

  • Redacts keys matching sensitive key patterns (password, secret, token, key, auth, cred).
  • Redacts string patterns matching Vercel Blob tokens (vercel_blob_rw_...).
  • Handles Error object properties (message, stack) and circular references safely using WeakSet.

βœ… Verification

Updated tests/unit/lib/error-reporting.test.ts with test cases confirming that sensitive keys and tokens are redacted as expected. All unit tests passed via pnpm test.


PR created automatically by Jules for task 15838035201127298316 started by @amrabed

Implement recursive sanitization in reportError to redact sensitive keys (passwords, tokens, API keys) and Vercel Blob tokens from logged errors and contexts.
@vercel

vercel Bot commented Aug 15, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
typescript Ready Ready Preview Aug 15, 2026 4:19am

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

@sonarqubecloud

Copy link
Copy Markdown

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.

0 participants