From owner-freebsd-security@freebsd.org Wed Jan 24 20:02:55 2018 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF921EC263E for ; Wed, 24 Jan 2018 20:02:55 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [209.237.23.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 856E4749E4 for ; Wed, 24 Jan 2018 20:02:55 +0000 (UTC) (envelope-from marquis@roble.com) Received: from roble.com (roble.com [209.237.23.50]) by mx5.roble.com (Postfix) with ESMTP id D081D4D33F; Wed, 24 Jan 2018 12:02:47 -0800 (PST) Date: Wed, 24 Jan 2018 12:02:47 -0800 (PST) From: Roger Marquis To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= cc: freebsd-security@freebsd.org Subject: Re: Malicious URL ? https://[::]/ In-Reply-To: <86shawfccq.fsf@desk.des.no> Message-ID: References: <86wp08fcil.fsf@desk.des.no> <86shawfccq.fsf@desk.des.no> MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 20:02:56 -0000 Dag-Erling Sm?rgrav wrote: > Hang on a sec ? localhost should be [::1], not [::], which is the > equivalent of 0.0.0.0. My guess is a software bug. Jails look a little > weird from the inside unless you use a fully virtualized network stack. > The proxy probably doesn't have sufficient error checking around > getpeername() or something like that. Another intermediate URL-checker reports that the plugin in question (CanvasBlocker) is requesting https://[::]/ directly. If a bug this is the first I've seen of it's kind. If not the question is what threat profile [::]:443 might expose. (Other than the obvious jail vector which really should be fixed. FreeBSD Foundation where are you?) Karl's reference to RFC 4291 indicates it is a protocol violation as well. The symptom has been reported to Mozilla. Roger