You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/08/31 13:16:22 UTC

[jira] [Resolved] (JCR-4009) CSRF in Jackrabbit-Webdav

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

Julian Reschke resolved JCR-4009.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.13.3

trunk: [r1758600|http://svn.apache.org/r1758600] [r1758597|http://svn.apache.org/r1758597]


> CSRF in Jackrabbit-Webdav
> -------------------------
>
>                 Key: JCR-4009
>                 URL: https://issues.apache.org/jira/browse/JCR-4009
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-webdav
>    Affects Versions: 2.6.5, 2.8.2, 2.10.3, 2.12.3, 2.13.2
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Blocker
>              Labels: csrf, security, webdav
>             Fix For: 2.13.3
>
>         Attachments: JCR-4009.diff
>
>
> The changes for JCR-4002 have disabled CRFS checking for POST, and thus leave the remoting servlet open for attacks. This HTML form below:
> {noformat}
> <form action="http://localhost:8080/server/default/jcr:root/" method="post">
>     <input type="text" id="name" name="user_name" />
>     <button type="submit">Send your message</button>
>     </form>
> {noformat}
> will successfully cross-origin-POST to jackrabbit-standalone.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)