GHSA-6c7v-2f49-8h26
Vulnerability from github
Published
2019-07-03 20:37
Modified
2024-09-18 16:15
Summary
Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS
Details

An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "Django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.1",
                  },
                  {
                     fixed: "2.1.10",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "PyPI",
            name: "Django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.2",
                  },
                  {
                     fixed: "2.2.3",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "PyPI",
            name: "Django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.11",
                  },
                  {
                     fixed: "1.11.22",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2019-12781",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-319",
      ],
      github_reviewed: true,
      github_reviewed_at: "2019-07-03T20:26:13Z",
      nvd_published_at: "2019-07-01T14:15:00Z",
      severity: "MODERATE",
   },
   details: "An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.",
   id: "GHSA-6c7v-2f49-8h26",
   modified: "2024-09-18T16:15:28Z",
   published: "2019-07-03T20:37:25Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2019-12781",
      },
      {
         type: "WEB",
         url: "https://docs.djangoproject.com/en/dev/releases/security",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-6c7v-2f49-8h26",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/django/django",
      },
      {
         type: "WEB",
         url: "https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2019-10.yaml",
      },
      {
         type: "WEB",
         url: "https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL",
      },
      {
         type: "WEB",
         url: "https://seclists.org/bugtraq/2019/Jul/10",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20190705-0002",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4043-1",
      },
      {
         type: "WEB",
         url: "https://www.debian.org/security/2019/dsa-4476",
      },
      {
         type: "WEB",
         url: "https://www.djangoproject.com/weblog/2019/jul/01/security-releases",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2019/07/01/3",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
         type: "CVSS_V3",
      },
      {
         score: "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
         type: "CVSS_V4",
      },
   ],
   summary: "Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.