Skip to content
Fencer Intel
medium 4.9

CVE-2018-16984 json

Django allows unprivileged users to read the password hashes of arbitrary accounts

published 8y ago modified 4mo ago also GHSA-6mx3-3vqg-hpp2 , PYSEC-2018-3 , EUVD-2018-0038

cvss
4.9
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 2.1.2
  • djangoproject django 2.1.2
  • python-Django5 openSUSE Tumbleweed 5.2.16-1.1
  • python-Django openSUSE Tumbleweed 5.2.16-1.1
  • python-Django4 openSUSE Tumbleweed 4.2.30-4.1
  • python-Django6 openSUSE Tumbleweed 6.0-1.1
  • python-Django4 openSUSE Tumbleweed 4.2.14-1.1
  • python-Django openSUSE Tumbleweed 3.2.7-2.3
  • python-Django openSUSE Tumbleweed 4.2.11-2.1

opensuse advisories openSUSE-SU-2026:11270-1openSUSE-SU-2026:11248-1openSUSE-SU-2026:11235-1openSUSE-SU-2026:10005-1openSUSE-SU-2024:14208-1openSUSE-SU-2024:11205-1

  • python-django Arch Linux 2.1.2-1

arch linux advisories AVG-773

Is CVE-2018-16984 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-16984 updated cvss 2.7

python-django: Password hash disclosure to "view only" admin users

  • Red Hat Ceph Storage 2 python-django, python-django-bash-completion Red Hat Certification for Red Hat Enterprise Linux 7 python-django Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) python-django, python-django-bash-completion Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) Operational Tools python-django, python-django-bash-completion Red Hat OpenStack Platform 8 (Liberty) python-django, python-django-bash-completion Red Hat OpenStack Platform 8 (Liberty) Operational Tools python-django, python-django-bash-completion
    +10 more products
    Red Hat OpenStack Platform 9 (Mitaka) python-django, python-django-bash-completion Red Hat OpenStack Platform 9 (Mitaka) Operational Tools python-django, python-django-bash-completion Red Hat OpenStack Platform 10 (Newton) python-django, python-django-bash-completion Red Hat OpenStack Platform 12 (Pike) python-django, python-django-bash-completion Red Hat OpenStack Platform 13 (Queens) python-django, python2-django, python-django-bash-completion Red Hat OpenStack Platform 14 (Rocky) python2-django, python-django-bash-completion Red Hat Satellite 6 python-django, python2-django, python-django-bash-completion Red Hat Storage 3 python-django, python2-django, python-django-bash-completion Red Hat Subscription Asset Manager Django Red Hat Update Infrastructure 3 for Cloud Providers python-django
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 4.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.0 4.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi django
>=2.1, <2.1.2
2.1.2

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.