From owner-svn-ports-all@freebsd.org Fri Feb 2 19:55:35 2018 Return-Path: Delivered-To: svn-ports-all@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 658D5EC2468; Fri, 2 Feb 2018 19:55:35 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16DAD7DB9B; Fri, 2 Feb 2018 19:55:35 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 009E220405; Fri, 2 Feb 2018 19:55:34 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w12JtYvQ069634; Fri, 2 Feb 2018 19:55:34 GMT (envelope-from sunpoet@FreeBSD.org) Received: (from sunpoet@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w12JtYS3069632; Fri, 2 Feb 2018 19:55:34 GMT (envelope-from sunpoet@FreeBSD.org) Message-Id: <201802021955.w12JtYS3069632@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: sunpoet set sender to sunpoet@FreeBSD.org using -f From: Sunpoet Po-Chuan Hsieh Date: Fri, 2 Feb 2018 19:55:34 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r460749 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: sunpoet X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 460749 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 19:55:35 -0000 Author: sunpoet Date: Fri Feb 2 19:55:34 2018 New Revision: 460749 URL: https://svnweb.freebsd.org/changeset/ports/460749 Log: Document django vulnerability Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Fri Feb 2 19:55:28 2018 (r460748) +++ head/security/vuxml/vuln.xml Fri Feb 2 19:55:34 2018 (r460749) @@ -58,6 +58,56 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + Django -- information leakage + + + py27-django111 + py34-django111 + py35-django111 + py36-django111 + 1.11.10 + + + py27-django20 + py34-django20 + py35-django20 + py36-django20 + 2.0.2 + + + + +

Django release notes:

+
CVE-2018-6188: Information leakage in AuthenticationForm
+
A regression in Django 1.11.8 made AuthenticationForm run its + confirm_login_allowed() method even if an incorrect password is entered. + This can leak information about a user, depending on what messages + confirm_login_allowed() raises. If confirm_login_allowed() isn't + overridden, an attacker enter an arbitrary username and see if that user + has been set to is_active=False. If confirm_login_allowed() is + overridden, more sensitive details could be leaked.
+
This issue is fixed with the caveat that AuthenticationForm can no + longer raise the "This account is inactive." error if the authentication + backend rejects inactive users (the default authentication backend, + ModelBackend, has done that since Django 1.10). This issue will be + revisited for Django 2.1 as a fix to address the caveat will likely be too + invasive for inclusion in older versions.
+

+ + + + https://docs.djangoproject.com/en/1.11/releases/1.11.10/ + https://docs.djangoproject.com/en/2.0/releases/2.0.2/ + CVE-2018-6188 + + + 2018-02-01 + 2018-02-02 + + + w3m - multiple vulnerabilities