This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Mod csrfprotector"
A V Minhaz (talk | contribs) |
A V Minhaz (talk | contribs) |
||
Line 1: | Line 1: | ||
<h2>mod_csrfprotector - Apache 2.x.x Modules for mitigating CSRF attacks</h2> | <h2>mod_csrfprotector - Apache 2.x.x Modules for mitigating CSRF attacks</h2> | ||
− | |||
− | |||
==What is mod_csrfprotector== | ==What is mod_csrfprotector== | ||
Line 19: | Line 17: | ||
==Damages Mitigated== | ==Damages Mitigated== | ||
* Cross Site Request Forgery | * Cross Site Request Forgery | ||
− | |||
==How to contribute== | ==How to contribute== | ||
Line 28: | Line 25: | ||
==Current Status== | ==Current Status== | ||
− | + | Under Development | |
+ | |||
+ | __NOTOC__ <headertabs /> | ||
+ | |||
+ | [[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] |
Revision as of 18:06, 24 June 2014
mod_csrfprotector - Apache 2.x.x Modules for mitigating CSRF attacks
What is mod_csrfprotector
Its an Apache 2.x.x Module (Currently 2.2.x) under development. It can be installed and configured in any Apache Server to protect it against Cross Site Request Forgery attacks. mod_csrfprotector provides protection to both POST and GET requests (not enabled by default).
How mod_csrfprotector works?
Once installed in Apache Server, every request that is made to the server, and validated against CSRF attacks by the input filters. Input filter follows a protocol as mentioned by developer in configuration, which helps the module to decide weather to validated the request. The input filter checks for appropriate token sent with request. Request if forwarded to other filters or content generator (like php or cgi) in validation is successful. Otherwise, appropriate actions are taken as per configuration. For ex: 403, Forbidden header is send to client. The Output filter, checks for content type of output generated by content generator and if it is `text/html` or `text/xhtml` it appends javascript code to the output. This js code in client side is responsible for attaching CSRFP_token with every required request sent from client.
Features Offered
CSRF Protection provide protection for:
- Normal HTML forms (POST/GET)
- Normal Get requests (Not enabled by default)
- Ajax Requests (XHR)
- Dynamically generated forms
Damages Mitigated
- Cross Site Request Forgery
How to contribute
To contribute to the code fork and send a pull to:
GitHub Repo - mod_csrfprotector
For discussions, join our mailing list: - Mailing List
Current Status
Under Development