Skip to content

πŸ›‘οΈ Sentinel: [CRITICAL] Fix bcrypt timing attack and DoS vulnerabilities#49

Open
luisdlopera wants to merge 2 commits into
mainfrom
sentinel/fix-bcrypt-timing-and-dos-5413427270839107431
Open

πŸ›‘οΈ Sentinel: [CRITICAL] Fix bcrypt timing attack and DoS vulnerabilities#49
luisdlopera wants to merge 2 commits into
mainfrom
sentinel/fix-bcrypt-timing-and-dos-5413427270839107431

Conversation

@luisdlopera
Copy link
Copy Markdown
Owner

🚨 Severity: CRITICAL
πŸ’‘ Vulnerability:

  1. The dummy hash used to mitigate timing attacks when a user is not found was invalid, causing bcrypt.compare to return almost instantly and enabling user enumeration.
  2. Password fields in auth DTOs lacked maximum length constraints, allowing for Denial of Service (DoS) via CPU exhaustion when processing excessively long strings with bcrypt.
    🎯 Impact: Attackers could enumerate valid email addresses and crash/overload the server by submitting massive passwords.
    πŸ”§ Fix:
  3. Replaced the dummy string with a validly formatted bcrypt hash of equivalent cost.
  4. Added @MaxLength(100) validation to all relevant password fields in DTOs.
    βœ… Verification: Ran the test suite successfully and verified that a dummy comparison takes the same amount of time as a normal one. Length constraints are validated via class-validator.

PR created automatically by Jules for task 5413427270839107431 started by @luisdlopera

- Replaced invalid dummy bcrypt hash with a valid one to prevent timing attacks (user enumeration).
- Added @maxlength(100) to password fields in Auth DTOs to prevent CPU exhaustion DoS attacks during hashing.
@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.

- Replaced invalid dummy bcrypt hash with a valid one to prevent timing attacks (user enumeration).
- Added @maxlength(100) to password fields in Auth DTOs to prevent CPU exhaustion DoS attacks during hashing.
- Wrapped Next.js useSearchParams in a Suspense boundary in auth page to fix build failure.
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