π‘οΈ Sentinel: Fix information leakage in login_required error response - #22
Conversation
Omit raw exception details from the JSON error payload in login_required to avoid leaking internal system details or credentials to untrusted clients. Exception details are now safely logged server-side. 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 Security Fix: Prevent Information Leakage in Authentication
π¨ Severity: MEDIUM
π‘ Vulnerability: Raw exception messages (
str(e)) were returned in JSON responses by thelogin_requireddecorator when JWT verification failed or errors occurred.π― Impact: Untrusted clients could receive internal system details, database connection strings, or stack trace fragments.
π§ Fix: Omitted raw exception string from response payload and logged it server-side using
logger.exception().β Verification: Added unit test
tests/test_auth_utils.pyverifying that exception details are not present in error responses and ran unittest suite.PR created automatically by Jules for task 2465454228130646528 started by @Pmaster-dev