CVE-2018-6188: Infoleak
First published: Mon Feb 05 2018(Updated: )
`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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Djangoproject Django | =1.11.8 | |
| Djangoproject Django | =1.11.9 | |
| Djangoproject Django | =2.0 | |
| Djangoproject Django | =2.0.1 | |
| Canonical Ubuntu Linux | =17.10 | |
| debian/python-django | 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:4.2.16-1 | |
| pip/Django | >=2.0a1<2.0.2 | 2.0.2 |
| pip/django | >=1.11.8<1.11.10 | 1.11.10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2018-6188
- https://github.com/advisories/GHSA-rf4j-j272-fj86 (Advisory)
- https://usn.ubuntu.com/3559-1/
- https://www.djangoproject.com/weblog/2018/feb/01/security-releases/
- http://www.securitytracker.com/id/1040422
- https://launchpad.net/bugs/cve/CVE-2018-6188
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6188
- https://security-tracker.debian.org/tracker/CVE-2018-6188
- https://ubuntu.com/security/CVE-2018-6188
- https://github.com/django/django/commit/57b95fedad5e0b83fc9c81466b7d1751c6427aae
- https://github.com/django/django/commit/c37bb28677295f6edda61d8ac461014ef0d3aeb2
- https://usn.ubuntu.com/3559-1
- https://www.djangoproject.com/weblog/2018/feb/01/security-releases
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2018-4.yaml
- https://web.archive.org/web/20200517143909/http://www.securitytracker.com/id/1040422
Frequently Asked Questions
What is the severity of CVE-2018-6188?
The severity of CVE-2018-6188 is high with a CVSS score of 7.5.
How does CVE-2018-6188 affect Django?
CVE-2018-6188 affects Django versions 1.11.8, 1.11.9, 2.0 before 2.0.2.
How can remote attackers exploit CVE-2018-6188?
Remote attackers can exploit CVE-2018-6188 by leveraging data exposure from the confirm_login_allowed() method in django.contrib.auth.forms.AuthenticationForm to obtain potentially sensitive information.
Which versions of Django are affected by CVE-2018-6188?
Django versions 1.11.8, 1.11.9, 2.0 before 2.0.2 are affected by CVE-2018-6188.
How do I fix CVE-2018-6188?
To fix CVE-2018-6188, update Django to version 1.11.10 for versions 1.11.8 and 1.11.9, or update to version 2.0.2 for versions 2.0 before 2.0.2.
- collector/nvd-index
- agent/type
- collector/launchpad-cve
- source/Launchpad
- agent/author
- agent/remedy
- agent/weakness
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/severity
- collector/mitre-cve
- source/MITRE
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/first-publish-date
- collector/security-tracker-debian
- source/Debian
- agent/event
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-rf4j-j272-fj86
- alias/CVE-2018-6188
- agent/last-modified-date
- agent/references
- agent/softwarecombine
- agent/tags
- collector/github-advisory
- vendor/djangoproject
- canonical/djangoproject django
- version/djangoproject django/1.11.8
- version/djangoproject django/1.11.9
- version/djangoproject django/2.0
- version/djangoproject django/2.0.1
- vendor/canonical
- canonical/canonical ubuntu linux
- version/canonical ubuntu linux/17.10
- package-manager/debian
- package-manager/pip