-
Notifications
You must be signed in to change notification settings - Fork 232
Security Fixes #2300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
KesterTan
wants to merge
1
commit into
master
Choose a base branch
from
security-fixes
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Security Fixes #2300
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
CSRF config is fragile; prefer default CSRF for all non‑GET requests (JSON included).
You’re skipping CSRF on destroy_batch/excuse_batch and re‑adding it only when request.format.json? is true. Two issues:
Safer: keep default CSRF for both HTML and JSON; clients should send X-CSRF-Token. Remove the exception and the conditional before_action.
Run to locate callers and confirm they set the CSRF header:
Apply this minimal change:
🏁 Script executed:
Length of output: 2671
🏁 Script executed:
Length of output: 173188
Remove the fragile CSRF bypass; use default Rails CSRF protection.
The current config is indeed vulnerable. Although your JavaScript correctly sends
X-CSRF-Tokenheaders, theexceptclause bypasses CSRF checks entirely, leaving HTML form submissions unprotected. The conditionalif: :json_request?is unreliable becauserequest.format.json?depends on the Accept header, not Content-Type, and AJAX calls may not consistently trigger it.Fix:
This works because your JavaScript clients already send the token in the
X-CSRF-Tokenheader (as confirmed in manage_submissions.js), and Rails will validate it automatically. HTML forms will also be protected by the default CSRF filter.📝 Committable suggestion
🤖 Prompt for AI Agents