/explore
|
You are here 
|
bogs.io | ||
| | | | |
smagin.fyi
Why do we have both CSRF protection and CORS? |
|
| | | | | ||
| | | | |
wouterj.nl
Cross-site Request Forgery (CSRF) is one of the traditional vulnerabilities that web applications have to deal with. Every web framework - including Symfony - supports CSRF protection out of the box. A lesser known vulnerability is Login CSRF, a special kind of CSRF attack. |
|
| | | | | ||
| | | | |
words.filippo.io
Cross-Site Request Forgery countermeasures can be greatly simplified using request metadata provided by modern browsers. |
|
| | | | | ||
| | | | |
mathieu.fenniak.net
Cross-site request forgery (CSRF) is a type of security exploit where a user's web browser is tricked by a third-party site into performing actions on websites that the user is logged into. It is often a difficult attack to pull off, as it requires a number of factors to line up at once. Protecting against it requires good discipline and good design practices, especially when it comes to protecting Web APIs. Here's a brief example of a fictitious CSRF attack against a bank: |
|
| | | |||
