This repository was archived by the owner on Apr 12, 2024. It is now read-only.
docs($http): reword of XSRF attack overview#13901
Closed
vucalur wants to merge 1 commit into
Closed
Conversation
Previous version emphasised "gaining user's private data". While this perfectly describes JSON vulnerability (which is based on XSRF), data theft suits XSS more. Pure XSRF is more about performing requests that have side effects.
gkalpak
pushed a commit
that referenced
this pull request
Jan 31, 2016
Previous version emphasised "gaining user's private data". While this perfectly describes JSON vulnerability (which is based on XSRF), data theft suits XSS more. Pure XSRF is more about performing requests that have side effects. Closes #13901
Member
|
I reworded it a bit and merged. Thx ! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Previous version emphasised "gaining user's private data".
While this perfectly describes JSON vulnerability (which is based on XSRF),
data theft suits XSS more.
Pure XSRF is more about performing requests that have side effects.