appsec.fyi › Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) Resources

Page 4 of 4: resources 151–154 of 154, added Feb 2017 to Apr 2018.

The newest Cross-Site Request Forgery (CSRF) resources are on the Cross-Site Request Forgery (CSRF) page. For a reading order instead of a date order, see the Cross-Site Request Forgery (CSRF) learning path.

Date AddedLinkExcerpt
2018-04-30 2018Steal CSRF/Auth/Unique key Header with XSS intermediate XSSThe content is incomplete and lacks specific information to provide a concise summary.
2018-04-06 2018A Deep Dive into CSRF Protection in Rails – Ruby Inside – Medium intermediateThe content discusses CSRF protection in Rails, with updates reflecting code changes in Rails 6 as of June 2019. CSRF protection is crucial for securing web applications against malicious attacks. The article likely delves into the mechanisms and best practices for implementing CSRF protection in Ruby on Rails applications, emphasizing the importance of staying updated with the latest changes to ensure robust security measures.
2018-01-02 20180ang3el/EasyCSRF beginner 2 min readLibrary for identifying weak CSRF protection in web applications, particularly effective against API endpoints and GraphQL. EasyCSRF modifies HTTP requests to bypass common protections like content type checks and token parameters, allowing researchers to manually analyze failed versus successful actions in Burp Suite's proxy history. It supports various parameter and header name configurations, request whitelisting, and conversion between data formats.
2017-02-22 2017Cross-Site Request Forgery is dead! intermediate 8 min readLibrary for implementing Same-Site Cookies to mitigate Cross-Site Request Forgery (CSRF) attacks. This simple attribute, when added to cookies, instructs browsers to prevent them from being sent with cross-origin requests, effectively neutralizing CSRF vulnerabilities without complex server-side logic. Options include Strict mode for absolute protection, preventing cookies on all cross-origin requests, and Lax mode, which allows cookies on top-level navigations using safe HTTP methods like GET.