π‘οΈ Sentinel: Fix sensitive error detail leakage in login_required - #25
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: Fix sensitive error detail leakage in login_required
π¨ Severity: MEDIUM
π‘ Vulnerability: The
login_requireddecorator inauth/utils.pyreturned raw exception details (str(e)) in 401 response payloads.π― Impact: An attacker could deliberately trigger auth exceptions to inspect internal stack traces or database/token errors.
π§ Fix: Removed
str(e)leakage and return generic{"error": "Unauthorized"}response.β Verification: Added unit tests in
tests/test_auth.pyverifying response behavior when JWT verification fails with exceptions.PR created automatically by Jules for task 4846975491480150802 started by @Pmaster-dev