π‘οΈ Sentinel: Prevent sensitive error detail leakage in login_required decorator - #31
Conversation
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
|
π 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. |
π‘οΈ Sentinel: [MEDIUM] Prevent sensitive error detail leakage in login_required decorator
π¨ Severity: MEDIUM
π‘ Vulnerability: Information Disclosure / Sensitive Error Details Leakage
π― Impact: Raw exception strings in login_required could leak internal stack/database details or sensitive internal variables to unauthenticated API clients.
π§ Fix: Removed 'details': str(e) from the error response returned by login_required in auth/utils.py.
β Verification: Added unit test in tests/test_auth_utils.py confirming login_required returns sanitized error response without leaking details.
PR created automatically by Jules for task 3816073396050230108 started by @Pmaster-dev