Talk:Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet

Revision as of 17:41, 24 August 2012 by Michael Brooks (Talk | contribs)

Jump to: navigation, search

Checking Referer Header is used to patch the most dangerous CSRF vulnerability ever discovered (which was by me Michael Brooks). This article is incorrect and I am chaining it. If you have a problem then you should contact me, but as it stands I cannot allow this page to spread false information.

That is not the most dangerous CSRF vuln ever discovered! You are either really full of yourself, or you know very little about CSRF. I have found CSRF bugs that could have trivially been exploited for millions of dollars of theft, and those aren't the worst ones out there. I'm going to update the Referer Header section to be more accurate and include GET-based CSRF attacks (such as open redirection, probably from the login page) that referer checking usually doesn't cover either (which is one of it's biggest flaws).

Don't post theoretical attacks, or "here say" on any OWASP page.

Look people. A referer check is a valid form of protection and is currently being used to stop the most dangerous CSRF vulnerability ever discovered (according to the DHS: If you think it be exploited, PROVE IT. Stop spreading clearly false information on OWASP.

Write an exploit and show me that it works. Then you can change the owasp wiki.