Re: [Acme] Alternative proposal for fixing TLS-SNI / revisiting HTTPS-01 authorization

Ilari Liusvaara <ilariliusvaara@welho.com> Fri, 12 January 2018 17:08 UTC

Return-Path: <ilariliusvaara@welho.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E0B612D80F for <acme@ietfa.amsl.com>; Fri, 12 Jan 2018 09:08:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L66eX9rG_g8T for <acme@ietfa.amsl.com>; Fri, 12 Jan 2018 09:08:51 -0800 (PST)
Received: from welho-filter4.welho.com (welho-filter4.welho.com [83.102.41.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CC56127978 for <acme@ietf.org>; Fri, 12 Jan 2018 09:08:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by welho-filter4.welho.com (Postfix) with ESMTP id A6D3C97A2F; Fri, 12 Jan 2018 19:08:49 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter4.welho.com [::ffff:83.102.41.26]) (amavisd-new, port 10024) with ESMTP id bs7ebxBTUEYz; Fri, 12 Jan 2018 19:08:49 +0200 (EET)
Received: from LK-Perkele-VII (87-92-19-27.bb.dnainternet.fi [87.92.19.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPSA id 5C2D22308; Fri, 12 Jan 2018 19:08:47 +0200 (EET)
Date: Fri, 12 Jan 2018 19:08:47 +0200
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: "Gerd v. Egidy" <gerd.von.egidy@intra2net.com>
Cc: acme@ietf.org
Message-ID: <20180112170847.GB31935@LK-Perkele-VII>
References: <1812883.r3FRolLa0t@thunder.m.i2n> <20180112164233.GA31841@LK-Perkele-VII> <4181164.OuRzJEQIXO@thunder.m.i2n>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <4181164.OuRzJEQIXO@thunder.m.i2n>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/b5Em6NeI8k7C0jzDrTvbJ_fiKKk>
Subject: Re: [Acme] Alternative proposal for fixing TLS-SNI / revisiting HTTPS-01 authorization
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2018 17:08:53 -0000

On Fri, Jan 12, 2018 at 06:03:34PM +0100, Gerd v. Egidy wrote:
> > That is still vulernable to default-vhost issues if:
> > 
> > - The hoster does not explicitly reserve default vhost (I have seen that
> >   kind of behavior with http:// too).
> > - The hoster lets customers upload arbitrary certificates.
> 
> I think you also need:
> 
> - A user is able to trick the server into serving his document root as default 
> vhost
> 
> - The webserver serves the default tls vhost, even if the CA requested a 
> specific vhost via SNI

Well, I think both are impiled by default vhost.
 
> > (And there are countermeasures that can detect default vhosts).
> 
> Could you explain in more detail?
> 
> Will they still work in conjunction with TLS and SNI?

One trick: Use some wild host value, and see that either TLS handshake
fails with alert 112, or that returned certificate is different.


-Ilari