🛡️ Sentinel: [CRITICAL] Fix fail-open file system access #20
Conversation
Fixed a critical security vulnerability where the server allowed access to the entire file system if no `--allowed-workspace` arguments were provided. Changes: - Changed `validateAllowedPath` to throw an error if no workspaces are configured (fail secure). - Updated CLI entry point to default to `process.cwd()` if no arguments are provided, maintaining usability while improving security. - Updated tests to verify the new secure behavior. - Added Sentinel journal entry.
|
👋 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. |
Fixed a critical vulnerability where missing configuration resulted in full file system access. The server now defaults to the current working directory if no workspaces are explicitly allowed, and the internal validation logic now denies access by default if the configuration is empty.
PR created automatically by Jules for task 771577714099202422 started by @GhostTypes