sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sonal Gupta (Jira)" <j...@apache.org>
Subject [jira] [Updated] (SLING-9043) COPY/MOVE should be in the referer filter's default list of protected HTTP methods
Date Mon, 10 Feb 2020 06:21:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sonal Gupta updated SLING-9043:
-------------------------------
    Description: 
The COPY/MOVE method , by default, are 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.

Note : With proper CORS configuration (such as the default) this issue is mitigated, CSRF
is not a problem for COPY/MOVE *unless* the attacked site has been configured to be wide
open for CORS access.

  was:
The COPY/MOVE method , by default, are 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.

Note : With proper CORS configuration this issue is mitigated, CSRF is not a problem for
COPY/MOVE *unless* the attacked site has been configured to be wide open for CORS access.


> COPY/MOVE 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
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The COPY/MOVE method , by default, are 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.
> Note : With proper CORS configuration (such as the default) this issue is mitigated, CSRF
is not a problem for COPY/MOVE *unless* the attacked site has been configured to be wide
open for CORS access.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message