Django 1.11.10 release notes¶
February 1, 2018
Django 1.11.10 fixes a security issue and several bugs in 1.11.9.
CVE-2018-6188: Information leakage in
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
overridden, an attacker enter an arbitrary username and see if that user has
been set to
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,
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
- Fixed incorrect foreign key nullification if a model has two foreign keys to the same model and a target model is deleted (#29016).
- Fixed a regression where
contrib.auth.authenticate()crashes if an authentication backend doesn’t accept
requestand a later one does (#29071).
- Fixed crash when entering an invalid uuid in