π‘οΈ Sentinel: [CRITICAL] Fix PII leak in Sentry attribution#222
π‘οΈ Sentinel: [CRITICAL] Fix PII leak in Sentry attribution#222google-labs-jules[bot] wants to merge 1 commit into
Conversation
|
π 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
π¨ Severity: CRITICAL
π‘ Vulnerability: User email added to SentrySDK leaked into global scope on throw.
π― Impact: Subsequent events would wrongly contain this PII.
π§ Fix: Used defer to clear user upon block exit.
β Verification: Code review confirms cleanup via defer.
PR created automatically by Jules for task 139653031811761464 started by @TytaniumDev