feat(security): implement CSRF protection middleware#775
Merged
Conversation
- Add CSRF middleware using synchronizer token pattern with session storage - Generate tokens with crypto.randomBytes(32) for sufficient entropy - Use timingSafeEqual for constant-time comparison to prevent timing attacks - Rotate token after each state-changing request to prevent replay attacks - Skip CSRF validation for OPTIONS requests (CORS preflight) and JWT-authenticated requests (Bearer token auth is not CSRF-vulnerable) - Expose current token via X-CSRF-Token response header on safe methods - Session SameSite=strict cookie policy already enforced in session config closes rinafcode#526
|
@walexjnr Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
RUKAYAT-CODER
approved these changes
Jun 24, 2026
RUKAYAT-CODER
left a comment
RUKAYAT-CODER
left a comment
Contributor
There was a problem hiding this comment.
Thank you for contributing to the project
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements CSRF protection for all state-changing endpoints using the synchronizer token pattern backed by the existing Redis session store.
What's changed
closes #526