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/06 10:28:00 UTC
[jira] [Comment Edited] (SLING-9043) COPY should be in the referer
filter's default list of protected HTTP methods
[ https://issues.apache.org/jira/browse/SLING-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031442#comment-17031442 ]
Konrad Windszus edited comment on SLING-9043 at 2/6/20 10:27 AM:
-----------------------------------------------------------------
As the referrer is very often disabled in browsers one should IMHO rather rely on the origin header to prevent such kind of attack (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin). AFAIK the origin header cannot be disabled (https://www.sjoerdlangkemper.nl/2019/02/27/prevent-csrf-with-the-origin-http-request-header/)
was (Author: kwin):
As the referrer is very often disabled in browsers one should IMHO rather rely on the origin header to prevent such kind of attack (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin). AFAIK the origin header cannot be disabled!
> COPY should be in the referer filter's default list of protected HTTP methods
> -----------------------------------------------------------------------------
>
> Key: SLING-9043
> URL: https://issues.apache.org/jira/browse/SLING-9043
> Project: Sling
> Issue Type: Bug
> Components: Resource Access Security
> Reporter: Sonal Gupta
> Priority: Major
> Labels: vulnerability
>
> The COPY method , by default, is not in the list of methods covered by the CSRF Referer filter. This might allow an attacker to copy files (abusing the privileges of a logged in victim) using CSRF.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)