🛡️ Sentinel: [CRITICAL/HIGH] Fix path validation unhandled exceptions

[socialawy-dev]

🚨 Severity: HIGH
💡 Vulnerability: validate_path_within and SafeStaticFiles.get_response crashed with TypeError/AttributeError when supplied with None inputs, potentially failing open and bypassing security checks or causing a Denial of Service.
🎯 Impact: Unhandled exception in security middleware could lead to an information leak or DoS, and path traversal protection could fail on malformed inputs.
🔧 Fix: Explicitly check for path is None in SafeStaticFiles. Update validate_path_within except block to catch TypeError and AttributeError caused by resolving null paths.
✅ Verification: Covered by test_validate_path_within_none and existing route tests. Verified no regressions in path validation handling.

---

PR created automatically by Jules for task 17385339621401961955 started by @socialawy

[google-labs-jules]

👋 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.

[gemini-code-assist]

Code Review

This pull request addresses vulnerabilities related to unhandled exceptions in path handling by adding None checks in SafeStaticFiles and expanding exception handling in validate_path_within. It also includes updated security documentation and new unit tests for these edge cases. The reviewer recommends replacing the broad exception handling in validate_path_within with explicit None checks to prevent masking logic errors and ensure consistency with the project's security guidelines.

[gemini-code-assist]

While adding TypeError and AttributeError to the except block prevents crashes from None or malformed inputs, wrapping the entire function body in such a broad catch-all can mask potential logic errors or bugs introduced during future refactoring.

Following the 'Prevention' advice in .jules/sentinel.md (lines 13 and 18), it would be cleaner to explicitly check for None at the beginning of the function. This avoids the unexpected behavior of str(None) becoming the string "None" (which might pass the preliminary string check if the root is the current directory) and ensures that only expected type-related failures are caught during the resolution phase.