From owner-freebsd-bugs@freebsd.org Sun Jun 5 13:19:00 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87E80B6A417 for ; Sun, 5 Jun 2016 13:19:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0121949 for ; Sun, 5 Jun 2016 13:19:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u55DJ0d7050465 for ; Sun, 5 Jun 2016 13:19:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210049] jails & the default lo0 127.0.0.1 loopback interface Date: Sun, 05 Jun 2016 13:19:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: qjail1@a1poweruser.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2016 13:19:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210049 Bug ID: 210049 Summary: jails & the default lo0 127.0.0.1 loopback interface Product: Base System Version: 10.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: qjail1@a1poweruser.com The undocumented behavior of non-vimage jails populated with an port or pkg that defaults to communicating over the lo0 127.0.0.1 loopback interface is= to simply map it over with the jails defined primary IP address. This default = jail behavior exposes that port/pkg to all the traffic entering the jail over its primary IP address whether from the LAN or public network. This is a securi= ty issue.=20 This is not the behavior of 127.0.0.1 as defined in [RFC1700, page 5] which states "127.0.0.0/8 - This block is assigned for use as the Internet host= =20=20 loopback address. A datagram sent by a higher level protocol to an address anywhere within this block should loop back inside the host." In a jails c= ase the word "host" would also mean "jail". The administrators of such jails have to manually activate loopback by addi= ng lo0:127.0.0.x to the jails ip4_addr parameter value alone with the jails primary IP address. Then manually change the conf file of all the applicati= ons running in that jail to use that lo0 127.0.0.x IP address. Or an alternate = is to add a statement to the hosts rc.conf to clone the lo0 interface and them code as above. This means each jail has a unique loopback ip address.=20 This manual work around is not documented and should not be necessary. The non-vimage jail should just handle loopback localhost by default. The kernel lo0 interface needs to be made jail aware. This issue has been recently discussed with James Gritton jamie@freebsd.org= and he agrees its time to address this long outstanding security issue. --=20 You are receiving this mail because: You are the assignee for the bug.=