Django security releases issued: 2.0.2 and 1.11.10

In accordance with our security release policy, the Django team is issuing Django 1.11.10 and Django 2.0.2. These release addresses the security issue detailed below.

We encourage all users of Django to upgrade as soon as possible.

CVE-2018-6188: Information leakage in AuthenticationForm

A regression in Django 1.11.8 made
django.contrib.auth.forms.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.

Thanks Jack Cushman for reporting this issue.

Affected supported versions

  • Django master branch
  • Django 2.0 and 2.0.1
  • Django 1.11.8 and 1.11.9

Per our supported versions policy, Django 1.10 and 1.9 are no longer supported (but aren’t affected). Django 1.8 LTS (for which security support ends on April 1) is unaffected.

Resolution

Patches to resolve the issue have been applied to Django’s master branch and
the 2.0 and 1.11 release branches. The patches may be obtained from the following changesets:

The following releases have been issued:

The PGP key ID used for these releases is Tim Graham: 1E8ABDC773EDE252.

General notes regarding security reporting

As always, we ask that potential security issues be reported via
private email to security@djangoproject.com, and not via Django’s
Trac instance or the django-developers list. Please see our security
policies
for further
information.

Original Source

Leave a comment