Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix error disclosure and enforce JWT secret - #28

Open
Pmaster-dev wants to merge 1 commit into
copilot/restructure-repo-into-prod-devfrom
sentinel/fix-auth-security-disclosure-16330162437952022102
Open

Pmaster-dev wants to merge 1 commit into
copilot/restructure-repo-into-prod-devfrom
sentinel/fix-auth-security-disclosure-16330162437952022102

Conversation

@Pmaster-dev

Copy link
Copy Markdown
Owner

πŸ›‘οΈ Sentinel: Fix error disclosure and hardcoded JWT fallback secret

🚨 Severity: HIGH
πŸ’‘ Vulnerability:

  1. login_required decorator returned details: str(e) in 401 Unauthorized responses, exposing internal exception strings and stack traces to unauthenticated callers.
  2. JWTUtils defaulted to an insecure hardcoded secret ('jwt-secret') when JWT_SECRET_KEY environment variable was omitted.

🎯 Impact:

  1. Information leakage of internal system / database / authentication error details to unauthenticated clients.
  2. Token forgery if deployed without explicitly defining JWT_SECRET_KEY.

πŸ”§ Fix:

  1. Removed details: str(e) from login_required error response.
  2. Enforced requiring JWT_SECRET_KEY in JWTUtils, throwing an error or failing gracefully if missing instead of using a fallback.
  3. Added unit tests in tests/test_auth_utils.py to verify no error details are leaked and JWTUtils environment variable constraints are enforced.

βœ… Verification:

  • All 4 tests in tests/test_auth_utils.py pass.

PR created automatically by Jules for task 16330162437952022102 started by @Pmaster-dev

- Remove 'details': str(e) from login_required to prevent leaking
  exception details to unauthenticated callers.
- Require JWT_SECRET_KEY environment variable in JWTUtils rather
  than falling back to a hardcoded default secret.
- Update deprecated datetime.utcnow() usages to datetime.now(timezone.utc).
- Add unit tests in tests/test_auth_utils.py.

Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

πŸ‘‹ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant