Re:Reflected File Download: A New Web Attack Vector
by Someone1234 on Wednesday November 05, 2014 @06:16PM
(#8564851)
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.
[ Parent
| on HN ]
Re:Reflected File Download: A New Web Attack Vector
by Ded7xSEoPKYNsDd on Thursday November 06, 2014 @04:01AM
(#8566299)
It'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.
Re:Reflected File Download: A New Web Attack Vector
by Someone1234 on Thursday November 06, 2014 @10:17AM
(#8567339)
That form wouldn't be on the same domain and therefore would hit CSRF protections.
Re:Reflected File Download: A New Web Attack Vector
by Ded7xSEoPKYNsDd on Thursday November 06, 2014 @03:18PM
(#8569485)
Yes, 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.