Potential fix for code scanning alert no. 1: Disabled Spring CSRF protection - #115
Closed
cheestree wants to merge 1 commit into
Closed
Potential fix for code scanning alert no. 1: Disabled Spring CSRF protection#115cheestree wants to merge 1 commit into
cheestree wants to merge 1 commit into
Conversation
…tection Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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.
Potential fix for https://github.com/cheestree/vetly/security/code-scanning/1
The best fix is to remove explicit CSRF disabling in the
devsecurity chain so Spring Security’s default CSRF protection remains active. This preserves existing behavior as much as possible while eliminating the vulnerability pattern flagged by CodeQL.Concretely, in
src/server/src/main/kotlin/com/cheestree/vetly/config/SecurityConfig.kt, editdevSecurityFilterChainand delete the line:.csrf { it.disable() }No new methods or imports are required. Spring will apply its default CSRF protection automatically.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.