🛡️ Sentinel: [HIGH] Fix local information disclosure in state storage - #97
🛡️ Sentinel: [HIGH] Fix local information disclosure in state storage#97google-labs-jules[bot] wants to merge 1 commit into
Conversation
- Adds proper 0o700 and 0o600 permissions to state directory and file creation respectively to prevent information leakage to other local users.
|
👋 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.
|
🚨 Severity: HIGH
💡 Vulnerability: Local state file (
~/.polyagent/state.json) was created with default OS permissions, potentially exposing sensitive session data to other users on the local machine.🎯 Impact: Local information disclosure (LFI/Permissions) could leak API responses and agent session data to unauthorized users.
🔧 Fix: Added explicit
0o700(directory) and0o600(file) mode attributes tomkdirSyncandwriteFileSyncwhen managing local state.✅ Verification: Run the application CLI which initiates state file creation and check the generated folder/file
chmodpermissions. Tests also ran perfectly locally.PR created automatically by Jules for task 6667688275527608655 started by @parvezk