CVE-2018-6188: Django Django Vulnerable To Information Leakage Vulnerability

HIGH
Advisory Identifier: GHSA-rf4j-j272-fj86
Share
CVSS 7.5
CWE-200
Published
Advisory Summary

CVE-2018-6188 is a HIGH (CVSS 7.5) django vulnerable to information leakage vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Django libraries in the PyPI ecosystem. The issue involves django vulnerable to information leakage in authenticationform. Remediation is available by upgrading affected packages to version 2.0.2, 1.11.10.

CVE-2018-6188 at a Glance

CVE Identifier CVE-2018-6188
GHSA Identifier GHSA-rf4j-j272-fj86
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Django
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2018-6188

To remediate this vulnerability, upgrade all affected Django dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Django fixed: 2.0.2 
pip install Django>=2.0.2
Django fixed: 1.11.10 
pip install Django>=1.11.10
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show Django

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2018-6188, inspect your installed packages using pip:

pip show Django

Analyze the terminal output to locate any version of Django in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.2), your application is affected.

Note: The pip show Django command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Django, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

`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.

CVE-2018-6188 Affected Django Versions

2 component(s)
Fixed Versions:
2.0.21.11.10
Product / Package Ecosystem Affected Versions Fixed Version
Django
pypi/Django
PyPI
≥ 2.0a1
< 2.0.2
2.0.2
Django
pypi/Django
PyPI
≥ 1.11.8
< 1.11.10
1.11.10

References

NVD — CVE-2018-6188 NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-6188
Security Fix Commit FIX COMMIT
https://github.com/django/django/commit/57b95fedad5e0b83fc9c81466b7d1751c6427aae
Security Fix Commit FIX COMMIT
https://github.com/django/django/commit/c37bb28677295f6edda61d8ac461014ef0d3aeb2
GitHub Advisory / Wiki ADVISORY
https://github.com/advisories/GHSA-rf4j-j272-fj86
Django Source Repository REPOSITORY
https://github.com/django/django
Django Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2018-4.yaml
usn.ubuntu.com/3559-1 WEB
https://usn.ubuntu.com/3559-1
Django Security Information SECURITY
https://web.archive.org/web/20200517143909/http://www.securitytracker.com/id/1040422
Django Release RELEASE
https://www.djangoproject.com/weblog/2018/feb/01/security-releases

Frequently Asked Questions

What is CVE-2018-6188?
CVE-2018-6188 is a security vulnerability in Django involving Django vulnerable to information leakage in AuthenticationForm under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Django versions are affected?
Affected versions include releases prior to 2.0.2, 1.11.10 across affected packages: Django.
What version fixes CVE-2018-6188?
Upgrading to 2.0.2, 1.11.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is Django affected?
Yes, Django is affected in releases prior to 2.0.2, 1.11.10. Upgrade your dependency to 2.0.2, 1.11.10 or later.
What is the CVSS score of CVE-2018-6188?
CVE-2018-6188 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2018-6188?
CVE-2018-6188 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check PyPI dependencies for CVE-2018-6188?
Run the dependency tree command: 'pip show Django'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rf4j-j272-fj86",
  "modified" : "2024-09-18T19:46:34Z",
  "published" : "2018-10-03T21:13:54Z",
  "aliases" : [ "CVE-2018-6188" ],
  "summary" : "Django vulnerable to information leakage in AuthenticationForm",
  "details" : "`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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "Django"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0a1"
      }, {
        "fixed" : "2.0.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "Django"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.11.8"
      }, {
        "fixed" : "1.11.10"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-6188"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django/django/commit/57b95fedad5e0b83fc9c81466b7d1751c6427aae"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django/django/commit/c37bb28677295f6edda61d8ac461014ef0d3aeb2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-rf4j-j272-fj86"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/django/django"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2018-4.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://usn.ubuntu.com/3559-1"
  }, {
    "type" : "WEB",
    "url" : "https://web.archive.org/web/20200517143909/http://www.securitytracker.com/id/1040422"
  }, {
    "type" : "WEB",
    "url" : "https://www.djangoproject.com/weblog/2018/feb/01/security-releases"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-06-16T21:54:30Z",
    "nvd_published_at" : null
  }
}