π‘οΈ Sentinel: Add Trusted Types to Content Security Policy - #159
π‘οΈ Sentinel: Add Trusted Types to Content Security Policy#159keough99 wants to merge 1 commit into
Conversation
Co-authored-by: keough99 <13394623+keough99@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. |
π¨ Severity: ENHANCEMENT
π‘ Vulnerability: While active scripts do not use unsafe DOM sinks, unused vendor scripts in
/assetscontaininnerHTMLusages. If accidentally loaded or if future code introduces sinks, the site could be exposed to DOM-based XSS.π― Impact: Completely neutralizes DOM-based XSS attacks by instructing the browser to block all string-to-DOM sink assignments.
π§ Fix: Enhanced the Content-Security-Policy
<meta>tag across all HTML pages by addingrequire-trusted-types-for 'script'; trusted-types 'none';.β Verification: Start a local server, navigate to any page, and verify via Developer Tools that Trusted Types are enforced and no functionality is broken.
PR created automatically by Jules for task 14118620678270979432 started by @keough99