[Security] Harden client ID generation#7971
Conversation
Hardens client ID generation in ExtensionServerClient by using globalThis.crypto.randomUUID() when available, falling back to Math.random() for compatibility. Added unit tests to verify both the secure path and the fallback.
|
👋 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 the client ID generation by using a cryptographically secure random number generator when available.
WHAT is this pull request doing?
Replaces the insecure
Math.random()based client ID generation inExtensionServerClientwithglobalThis.crypto.randomUUID()when supported by the environment, maintaining a fallback for compatibility.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 16556810634221208946 started by @gonzaloriestra