svn commit: r460749 - head/security/vuxml

Fri Feb 2 19:55:35 UTC 2018

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.)
 -->
 <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+  <vuln vid="d696473f-9f32-42c5-a106-bf4536fb1f74">
+    <topic>Django -- information leakage</topic>
+    <affects>
+      <package>
+	<name>py27-django111</name>
+	<name>py34-django111</name>
+	<name>py35-django111</name>
+	<name>py36-django111</name>
+	<range><lt>1.11.10</lt></range>
+      </package>
+      <package>
+	<name>py27-django20</name>
+	<name>py34-django20</name>
+	<name>py35-django20</name>
+	<name>py36-django20</name>
+	<range><lt>2.0.2</lt></range>
+      </package>
+    </affects>
+    <description>
+      <body xmlns="http://www.w3.org/1999/xhtml">
+	<p>Django release notes:</p>
+	<blockquote cite="https://docs.djangoproject.com/en/1.11/releases/1.11.10/">
+	  <p>CVE-2018-6188: Information leakage in AuthenticationForm</p>
+	  <p>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.</p>
+	  <p>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.</p>
+	</blockquote>
+      </body>
+    </description>
+    <references>
+      <url>https://docs.djangoproject.com/en/1.11/releases/1.11.10/</url>
+      <url>https://docs.djangoproject.com/en/2.0/releases/2.0.2/</url>
+      <cvename>CVE-2018-6188</cvename>
+    </references>
+    <dates>
+      <discovery>2018-02-01</discovery>
+      <entry>2018-02-02</entry>
+    </dates>
+  </vuln>
+
   <vuln vid="e72d5bf5-07a0-11e8-8248-0021ccb9e74d">
     <topic>w3m - multiple vulnerabilities</topic>
     <affects>
