4 ms·
I wonder if this can be mitigated by marking your JSON actions as HTTP POST only. Since this utilises HTTP GET the request would never be actioned and since JSO
by Someone1234 12y ago
I wonder if this can be mitigated by marking your JSON actions as HTTP POST only. Since this utilises HTTP GET the request would never be actioned and since JSON uses HTTP POST almost exclusively it wouldn't break existing code.
- Ded7xSEoPKYNsDd 12y agoIt's not so hard to build a form and submit it automatically with JavaScript in order to get a user's browser to do a POST request to any URL you want.
- Someone1234 12y agoThat form wouldn't be on the same domain and therefore would hit CSRF protections.
- Ded7xSEoPKYNsDd 12y agoYes, if you require a user-specific random token in the request, the exploit doesn't work. But that's independent of GET/POST and not what you said in your earlier post.