🛡️ Sentinel: Fix direct sensitive path validation bypass - #21
Conversation
Ensure validate_path checks both direct input paths and realpath resolved paths against SENSITIVE_PATHS to prevent direct scanning of sensitive system directories. Add unit tests for path validation.
|
👋 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. |
1 participant
Fixed a security issue where direct sensitive paths (such as
/etc/shadowor/proc) were not checked againstSENSITIVE_PATHSinpath_validator.pyif they were not symlinks. Updatedvalidate_pathandnot_sensitive_pathto validate both direct and resolved paths against sensitive system locations and added unit tests intests/test_path_validator.py.PR created automatically by Jules for task 7606594139256619767 started by @D3M-Sudo