[Security] Harden URL sanitization#7700
Conversation
Hardens the URL sanitization logic to redact Basic Auth credentials (username and password) and expands the sensitive parameter list. The matching is now case-insensitive.
|
👋 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. |
WHY are these changes introduced?
Hardens URL sanitization to prevent leakage of sensitive credentials and tokens in logs or analytics.
WHAT is this pull request doing?
Implements redaction of URL credentials (username/password) and expands the list of sensitive query parameters to include common secret keys. The sanitization logic is also updated to be case-insensitive for search parameters.
How to test your changes?
CI
Checklist
patchfor bug fixes ·minorfor new features ·majorfor breaking changes) and added a changeset withpnpm changeset addPR created automatically by Jules for task 11338822784890241915 started by @gonzaloriestra