pysec-2018-3
Vulnerability from pysec
Published
2018-10-02 18:29
Modified
2021-06-10 06:50
Details

An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the "view" permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.

Impacted products
Name purl
django pkg:pypi/django



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "django",
            purl: "pkg:pypi/django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.1",
                  },
                  {
                     fixed: "2.1.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "2.1",
            "2.1.1",
         ],
      },
   ],
   aliases: [
      "CVE-2018-16984",
      "GHSA-6mx3-3vqg-hpp2",
   ],
   details: "An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the \"view\" permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.",
   id: "PYSEC-2018-3",
   modified: "2021-06-10T06:50:43.349902Z",
   published: "2018-10-02T18:29:00Z",
   references: [
      {
         type: "ARTICLE",
         url: "https://www.djangoproject.com/weblog/2018/oct/01/security-release/",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1041749",
      },
      {
         type: "ADVISORY",
         url: "https://security.netapp.com/advisory/ntap-20190502-0009/",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-6mx3-3vqg-hpp2",
      },
   ],
}


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.