🛡️ Sentinel: Fix exception details leakage in login_required decorator - #15
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. |
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
🛡️ Sentinel: Fix exposed exception details in authentication errors
Vulnerability
In
auth/utils.py, whenlogin_requiredfailed due to an exception, the JSON error response included'details': str(e), exposing internal implementation details and raw error messages to unauthenticated users.Fix
'details': str(e)from the 401 response payload.logger.exception.tests/test_auth.pyto verify that unauthorized requests return standard error responses without leaking exception details.PR created automatically by Jules for task 8388778677498683575 started by @Pmaster-dev