Django vulnerable to information leakage in AuthenticationForm
`django.contrib.auth.forms.AuthenticationForm` in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging data exposure from the `confirm_login_allowed()` method, as demonstrated by discovering whether a user account is inactive.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-6188US | high7.5 | — | ||
django.contrib.auth.forms.AuthenticationForm in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging da… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-rf4j-j272-fj86ADVISORY
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/57b95fedad5e0b83fc9c81466b7d1751c6427aaeWEB
- https://github.com/django/django/commit/c37bb28677295f6edda61d8ac461014ef0d3aeb2WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2018-4.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-6188ADVISORY
- https://usn.ubuntu.com/3559-1WEB
- https://web.archive.org/web/20200517143909/http://www.securitytracker.com/id/1040422WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan