feat: add CSRF protection for state-mutating API routes - #1127
Closed
smartalee wants to merge 7 commits into
Closed
Conversation
- Add double-submit cookie CSRF pattern with x-csrf-token header - Implement CSRF middleware with validation for POST/PATCH/DELETE - Exempt auth endpoints and GET/HEAD/OPTIONS from validation - Apply CSRF validation to notes, bookmarks, approvals, and tips routes Closes rinafcode#723
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
1 participant
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
Adds CSRF protection to all state-mutating API routes using the double-submit cookie pattern.
Changes
src/lib/csrfMiddleware.tswith CSRF token generation and validationsrc/middleware.tsto validate CSRF tokens on state-mutating requestsSecurity
API Endpoints Protected
/api/notes/api/bookmarks/api/approvals/api/tipsCloses #723