Fix code scanning alert no. 1: CSRF protection not enabled #23
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.
Fixes https://github.com/SOFware/close_encounters/security/code-scanning/1
To fix the CSRF vulnerability, we need to enable CSRF protection in the
ApplicationController
class. The best way to do this in a Rails application is to use theprotect_from_forgery
method with the:exception
strategy. This will raise an exception if an invalid CSRF token is encountered, providing a robust defense against CSRF attacks.Steps to implement the fix:
protect_from_forgery with: :exception
line to theApplicationController
class.test/dummy/app/controllers/application_controller.rb
file.Suggested fixes powered by Copilot Autofix. Review carefully before merging.