GHSA-hmr4-m2h5-33qx
Vulnerability from github
Published
2020-02-11 21:03
Modified
2024-09-20 15:03
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.3 (Critical) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Summary
SQL injection in Django
Details

Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "Django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "1.11.28",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "PyPI",
            name: "Django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.0",
                  },
                  {
                     fixed: "2.2.10",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "PyPI",
            name: "Django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "3.0",
                  },
                  {
                     fixed: "3.0.3",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2020-7471",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-89",
      ],
      github_reviewed: true,
      github_reviewed_at: "2020-02-05T15:07:21Z",
      nvd_published_at: null,
      severity: "CRITICAL",
   },
   details: "Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.",
   id: "GHSA-hmr4-m2h5-33qx",
   modified: "2024-09-20T15:03:11Z",
   published: "2020-02-11T21:03:20Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2020-7471",
      },
      {
         type: "WEB",
         url: "https://github.com/django/django/commit/001b0634cd309e372edb6d7d95d083d02b8e37bd",
      },
      {
         type: "WEB",
         url: "https://github.com/django/django/commit/505826b469b16ab36693360da9e11fd13213421b",
      },
      {
         type: "WEB",
         url: "https://github.com/django/django/commit/c67a368c16e4680b324b4f385398d638db4d8147",
      },
      {
         type: "WEB",
         url: "https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136",
      },
      {
         type: "WEB",
         url: "https://www.openwall.com/lists/oss-security/2020/02/03/1",
      },
      {
         type: "WEB",
         url: "https://www.djangoproject.com/weblog/2020/feb/03/security-releases",
      },
      {
         type: "WEB",
         url: "https://www.debian.org/security/2020/dsa-4629",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4264-1",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20200221-0006",
      },
      {
         type: "WEB",
         url: "https://security.gentoo.org/glsa/202004-17",
      },
      {
         type: "WEB",
         url: "https://seclists.org/bugtraq/2020/Feb/30",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ",
      },
      {
         type: "WEB",
         url: "https://groups.google.com/forum/#!topic/django-announce/X45S86X5bZI",
      },
      {
         type: "WEB",
         url: "https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2020-35.yaml",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/django/django",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-hmr4-m2h5-33qx",
      },
      {
         type: "WEB",
         url: "https://docs.djangoproject.com/en/3.0/releases/security",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2020/02/03/1",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
      {
         score: "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
         type: "CVSS_V4",
      },
   ],
   summary: "SQL injection in Django",
}


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.




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.