Skip to content

πŸ”’ Fix Insecure LocalStorage Usage#6

Open
artistso wants to merge 1 commit into
mainfrom
jules-fix-localstorage-security-6470512226870728574
Open

πŸ”’ Fix Insecure LocalStorage Usage#6
artistso wants to merge 1 commit into
mainfrom
jules-fix-localstorage-security-6470512226870728574

Conversation

@artistso

@artistso artistso commented Jul 6, 2026

Copy link
Copy Markdown
Owner

🎯 What: The vulnerability fixed was insecure local storage usage, which could expose sensitive data in a cross-site scripting (XSS) attack and ran into browser quota limitations for large drawing projects.
⚠️ Risk: While the impact is lower in a drawing application, storing potentially large sets of user-generated data or settings in LocalStorage presents a security weakness. It leaves user data vulnerable to theft if an XSS vulnerability were to be introduced elsewhere in the application, and the size limitations often cause unexpected bugs.
πŸ›‘οΈ Solution: Swapped localStorage usage with IndexedDB via the lightweight idb-keyval dependency. IndexedDB provides a more secure, modern web storage API that supports asynchronous interaction and handles larger amounts of data without hitting the tight quotas of LocalStorage. I've also implemented backward-compatibility logic to seamlessly migrate user data from LocalStorage to IndexedDB on their next visit, ensuring no data loss.


PR created automatically by Jules for task 6470512226870728574 started by @artistso

Migrated application state storage for projects and floating panel positions from `localStorage` to IndexedDB using the `idb-keyval` library.

Added logic to seamlessly migrate existing user data from `localStorage` over to IndexedDB upon first launch, and safely clean up the legacy `localStorage` keys.

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

Copy link
Copy Markdown

πŸ‘‹ 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