🔒 [security] Fix Stored XSS in Network page via dangerouslySetInnerHTML#194
🔒 [security] Fix Stored XSS in Network page via dangerouslySetInnerHTML#194
Conversation
Co-authored-by: scobru <1079164+scobru@users.noreply.github.com>
|
👋 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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🎯 What: The
⚠️ Risk: Stored Cross-Site Scripting (XSS). If left unfixed, an attacker could create a malicious post with a payload (e.g.,
item.contentwithin theNetworkpage was being rendered usingdangerouslySetInnerHTMLwithout any sanitization.<img src=x onerror=alert(1)>) that would execute arbitrary JavaScript in the context of any user viewing the Network page, potentially compromising user sessions or executing unwanted actions.🛡️ Solution: Integrated
dompurifyand wrappeditem.contentwithDOMPurify.sanitize(), effectively stripping out any malicious tags or attributes while preserving safe HTML formatting.PR created automatically by Jules for task 16140025727148014053 started by @scobru