Add CSRF token implementation for student app status update #163
Conversation
This file contains 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
Submit buttons can have values, so the extra hidden field is unnecessary.
wunc
approved these changes
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To address CSRF vulnerability #2641316 – Low – [profiles.utdallas.edu] CSRF at "/students/[VictimUsername]/status?status=drafted" in the HackerOne report.
Replaces the
<a>tag in the student form to update the student application status for a<form>element that contains the CSRF token used by theVerifyCsrfTokenmiddleware. Manual testing confirms that requests with an invalid or missing CSRF token return a 419 HTTP response.