pysec-2016-17
Vulnerability from pysec
Published
2016-12-09 20:59
Modified
2021-07-15 02:22
Details

Django 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 use a hardcoded password for a temporary database user created when running tests with an Oracle database, which makes it easier for remote attackers to obtain access to the database server by leveraging failure to manually specify a password in the database settings TEST dictionary.

Impacted products
Name purl
django pkg:pypi/django
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "django",
            purl: "pkg:pypi/django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.8",
                  },
                  {
                     fixed: "1.8.16",
                  },
                  {
                     introduced: "1.9",
                  },
                  {
                     fixed: "1.9.11",
                  },
                  {
                     introduced: "1.10",
                  },
                  {
                     fixed: "1.10.3",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "1.10",
            "1.10.1",
            "1.10.2",
            "1.8",
            "1.8.1",
            "1.8.10",
            "1.8.11",
            "1.8.12",
            "1.8.13",
            "1.8.14",
            "1.8.15",
            "1.8.2",
            "1.8.3",
            "1.8.4",
            "1.8.5",
            "1.8.6",
            "1.8.7",
            "1.8.8",
            "1.8.9",
            "1.9",
            "1.9.1",
            "1.9.10",
            "1.9.2",
            "1.9.3",
            "1.9.4",
            "1.9.5",
            "1.9.6",
            "1.9.7",
            "1.9.8",
            "1.9.9",
         ],
      },
   ],
   aliases: [
      "CVE-2016-9013",
   ],
   details: "Django 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 use a hardcoded password for a temporary database user created when running tests with an Oracle database, which makes it easier for remote attackers to obtain access to the database server by leveraging failure to manually specify a password in the database settings TEST dictionary.",
   id: "PYSEC-2016-17",
   modified: "2021-07-15T02:22:10.369344Z",
   published: "2016-12-09T20:59:00Z",
   references: [
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QXDKJYHN74BWY3P7AR2UZDVJREQMRE6S/",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OG5ROMUPS6C7BXELD3TAUUH7OBYV56WQ/",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1037159",
      },
      {
         type: "ADVISORY",
         url: "http://www.ubuntu.com/usn/USN-3115-1",
      },
      {
         type: "ARTICLE",
         url: "https://www.djangoproject.com/weblog/2016/nov/01/security-releases/",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/94069",
      },
      {
         type: "ADVISORY",
         url: "http://www.debian.org/security/2017/dsa-3835",
      },
   ],
}


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.