You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/02/10 11:18:00 UTC
[jira] [Commented] (SLING-9061) Evaluate ORIGIN header in addition
to Referer header in CSRFFilter
[ https://issues.apache.org/jira/browse/SLING-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033504#comment-17033504 ]
Konrad Windszus commented on SLING-9061:
----------------------------------------
For Ajax based attacks the Origin header seems much more reliable.
> Evaluate ORIGIN header in addition to Referer header in CSRFFilter
> ------------------------------------------------------------------
>
> Key: SLING-9061
> URL: https://issues.apache.org/jira/browse/SLING-9061
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Security 1.1.16
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Security 1.1.18
>
>
> As discussed in https://issues.apache.org/jira/browse/SLING-9043?focusedCommentId=17031442&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17031442 the origin header should be used to implement some CSRF protection. See also https://owasp.org/www-project-cheat-sheets/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#verifying-origin-with-standard-headers, https://seclab.stanford.edu/websec/csrf/csrf.pdf and https://www.sjoerdlangkemper.nl/2019/02/27/prevent-csrf-with-the-origin-http-request-header/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)