FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-04-16 06:42:40 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
d696473f-9f32-42c5-a106-bf4536fb1f74	Django -- information leakage 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. Discovery 2018-02-01 Entry 2018-02-02 py27-django111 py34-django111 py35-django111 py36-django111 < 1.11.10 py27-django20 py34-django20 py35-django20 py36-django20 < 2.0.2 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

VuXML ID

Description

d696473f-9f32-42c5-a106-bf4536fb1f74

Django -- information leakage

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.

Discovery 2018-02-01
Entry 2018-02-02
py27-django111
py34-django111
py35-django111
py36-django111

< 1.11.10

py27-django20
py34-django20
py35-django20
py36-django20

< 2.0.2

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