Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 55E4F200B73 for ; Mon, 29 Aug 2016 14:27:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5497E160AB8; Mon, 29 Aug 2016 12:27:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A46A1160AA7 for ; Mon, 29 Aug 2016 14:27:21 +0200 (CEST) Received: (qmail 11776 invoked by uid 500); 29 Aug 2016 12:27:20 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 11755 invoked by uid 99); 29 Aug 2016 12:27:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2016 12:27:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8EB412C0157 for ; Mon, 29 Aug 2016 12:27:20 +0000 (UTC) Date: Mon, 29 Aug 2016 12:27:20 +0000 (UTC) From: "Julian Reschke (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (JCR-4002) CSRF in Jackrabbit-Webdav using empty content-type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 29 Aug 2016 12:27:22 -0000 [ https://issues.apache.org/jira/browse/JCR-4002?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D154248= 12#comment-15424812 ]=20 Julian Reschke edited comment on JCR-4002 at 8/29/16 12:27 PM: --------------------------------------------------------------- But that means that code extending from this now will have to the CSRF prot= ection, right? If this is true, we need (a) to document that and (b) to rev= iew the existing code that *does* extend it (JSOP?), (c) figure out whether= code written by third-parties might be affected as well. was (Author: reschke): But that means that code extending from this now will have to the CSRF prot= ection, right? If this is true, we need (a) to document that and (b) to rev= iew the existing code that *does* extend it (JSOP?). > CSRF in Jackrabbit-Webdav using empty content-type > -------------------------------------------------- > > Key: JCR-4002 > URL: https://issues.apache.org/jira/browse/JCR-4002 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-webdav > Affects Versions: 2.4.5, 2.6.5, 2.8.2, 2.10.3, 2.12.3, 2.13.1 > Reporter: Dominique J=C3=A4ggi > Assignee: Dominique J=C3=A4ggi > Priority: Blocker > Labels: csrf, security, webdav > Fix For: 2.13.2 > > Attachments: JCR_4002__CSRF_in_Jackrabbit_Webdav_using_empty_cont= ent_type.patch > > > As per [0] the CSRF content-type check does not include a null request co= ntent type. This can be exploited to create a resource via CSRF like so: > {code} > > > > > > > {code} > I will mitigate this particular issue by including a null content type in= the list of rejected content types. > [0] https://github.com/cryptomator/cryptomator/issues/319 -- This message was sent by Atlassian JIRA (v6.3.4#6332)