Skip to content

🔒 Add Subresource Integrity (SRI) hashes for external resources - #19

Open
paul0728 wants to merge 1 commit into
mainfrom
fix/sri-integrity-check-768050110757342917
Open

🔒 Add Subresource Integrity (SRI) hashes for external resources#19
paul0728 wants to merge 1 commit into
mainfrom
fix/sri-integrity-check-768050110757342917

Conversation

@paul0728

Copy link
Copy Markdown
Collaborator

🎯 What:
Added missing Subresource Integrity (SRI) hashes when fetching external dependencies in docs/index.html.

  • Added an SRI hash to the <script> tag loading JSZip.
  • Added an SRI hash to the fetch options for magick.wasm.

⚠️ Risk:
If the external CDN (unpkg.com or cdnjs.cloudflare.com) was compromised or subject to a Man-In-The-Middle (MITM) attack, malicious code could be injected into the application. For the WASM binary, executing untrusted code within the browser context poses significant cross-site scripting (XSS) and remote code execution risks depending on browser zero-days.

🛡️ Solution:
Calculated the SHA-384 hashes for magick.wasm and jszip.min.js. Modified the respective fetch call and script tag to include the integrity option/attribute. This leverages native browser features to guarantee the fetched resources perfectly match the expected original files, aborting execution if they have been tampered with. Verified that the engine still initializes correctly using a headless Puppeteer browser test checking for SRI console errors.


PR created automatically by Jules for task 768050110757342917 started by @paul0728

Added Subresource Integrity (SRI) hashes to:
- The JSZip CDN script tag
- The fetch call for the magick.wasm WebAssembly binary

This mitigates the risk of a compromised CDN serving malicious code.

Co-authored-by: paul0728 <44644609+paul0728@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant