pysec-2020-31
Vulnerability from pysec
Published
2020-06-03 14:15
Modified
2021-01-20 15:15
Details

An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.

Impacted products
Name purl
django pkg:pypi/django
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "django",
            purl: "pkg:pypi/django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.2",
                  },
                  {
                     fixed: "2.2.13",
                  },
                  {
                     introduced: "3.0",
                  },
                  {
                     fixed: "3.0.7",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "2.2",
            "2.2.1",
            "2.2.2",
            "2.2.3",
            "2.2.4",
            "2.2.5",
            "2.2.6",
            "2.2.7",
            "2.2.8",
            "2.2.9",
            "2.2.10",
            "2.2.11",
            "2.2.12",
            "3.0",
            "3.0.1",
            "3.0.2",
            "3.0.3",
            "3.0.4",
            "3.0.5",
            "3.0.6",
         ],
      },
   ],
   aliases: [
      "CVE-2020-13254",
      "GHSA-wpjr-j57x-wxfw",
   ],
   details: "An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.",
   id: "PYSEC-2020-31",
   modified: "2021-01-20T15:15:00Z",
   published: "2020-06-03T14:15:00Z",
   references: [
      {
         type: "ARTICLE",
         url: "https://www.djangoproject.com/weblog/2020/jun/03/security-releases/",
      },
      {
         type: "WEB",
         url: "https://docs.djangoproject.com/en/3.0/releases/security/",
      },
      {
         type: "WEB",
         url: "https://groups.google.com/d/msg/django-announce/pPEmb2ot4Fo/X-SMalYSBAAJ",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4381-1/",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4381-2/",
      },
      {
         type: "ADVISORY",
         url: "https://security.netapp.com/advisory/ntap-20200611-0002/",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2020/06/msg00016.html",
      },
      {
         type: "ADVISORY",
         url: "https://www.debian.org/security/2020/dsa-4705",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/security-alerts/cpujan2021.html",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-wpjr-j57x-wxfw",
      },
   ],
}


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.