-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2018.0346
                       Django -- information leakage
                              5 February 2018

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           python-django
Publisher:         FreeBSD
Operating System:  FreeBSD
                   UNIX variants (UNIX, Linux, OSX)
                   Windows
Impact/Access:     Access Confidential Data -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2018-6188  

Original Bulletin: 
   http://www.vuxml.org/freebsd/d696473f-9f32-42c5-a106-bf4536fb1f74.html

Comment: This advisory references vulnerabilities in products which run on 
         platforms other than FreeBSD. It is recommended that administrators
         running python-django check for an updated version of the software 
         for their operating system.

- --------------------------BEGIN INCLUDED TEXT--------------------

Django -- information leakage

Affected packages
  py27-django111 < 1.11.10
  py34-django111 < 1.11.10
  py35-django111 < 1.11.10
  py36-django111 < 1.11.10
  py27-django20  < 2.0.2
  py34-django20  < 2.0.2
  py35-django20  < 2.0.2
  py36-django20  < 2.0.2

Details

VuXML ID  d696473f-9f32-42c5-a106-bf4536fb1f74
Discovery 2018-02-01
Entry     2018-02-02

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.

References

CVE Name CVE-2018-6188
URL      https://docs.djangoproject.com/en/1.11/releases/1.11.10/
URL      https://docs.djangoproject.com/en/2.0/releases/2.0.2/

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBWneli4x+lLeg9Ub1AQgdgRAAoLkex5CUT9/BmBLfmI5Eb9x2XlkU73gS
1rPg5Js8S24G8NVPsN9nFYbF+HZmqCfjcr03yhlcqy85jTfytjrFJS2sGGrfJBI9
NGwACbUDMlPIUPRcMOscOte43w/Sg/hga8Wuvyq75PCP4xUCb7D3O9XqDp8G7RN2
1lWbXnRxZwlzWDhV3pWj+JBgQ1K9t0tb3ldpKejfKh+uo6ninikz1uVwS7cpNH9e
SFP9aJQqHwmFz7OS7SSa73myj7Xp4XN6uyJVaM0x3d4qrHUZ+MPmwEZYHZqWlT9p
38l/m3rpqxd/BggPbmvPrswcZkgyGIv48TUIEBfMgNzjHzwk9AqN/+MHd5mO6xA4
4iveEjwJTx4gOc2x3CGpBpYs0SMeK33oaib6GXgQMHwZ/ePh9+edWIUkksunQd76
tLsgg9/po9Z+32ywU8wridU4CWuLy20mhlce3WDnPn86bU3WeEWMRwjkKhakDqSg
eL0S6DGe+WD75ZK4BjC4LWU82kd8I8gDvDDc/T2rYn/Uy+3+Pkk6a0SvNNU8pfot
9ySsf9bOetIxAGsoTxBmDyQx0UPcZ6tn64zRx93iXrwsR1iU6B8GtupYEhe8a9lt
T0wKXuSQ7MASSy94hKQmUIOfduNhPI4EmU/zkGTQh0w3+L4TWHTEGOiPw8QHb/a7
+KZQgXbcBi8=
=KFGe
-----END PGP SIGNATURE-----