Skip to content
Fencer Intel
low 3.1

CVE-2016-2513 json

Django User Enumeration Vulnerability

published 2016-04-08 10 y ago modified 2026-06-17 4 mo ago also GHSA-fp6p-5xvw-m74f , PYSEC-2016-16 , EUVD-2016-0005

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

Summary

The password hasher in contrib/auth/hashers.py in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to enumerate users via a timing attack involving login requests.

Patch / fix

  • pypi django 1.8.10, 1.9.3
  • python-django Debian 14, Debian 13, Debian 12 1.9.4-1

debian advisories DEBIAN-CVE-2016-2513

  • python-django Ubuntu 14.04 LTS 1.6.1-2ubuntu0.12

ubuntu advisories UBUNTU-CVE-2016-2513

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-django openstack-optools 7, openstack 6, openstack 5 1.6.11-5.el7ost
  • python-django-bash-completion openstack-optools 7, openstack 6, openstack 5 1.6.11-5.el7ost
  • python-django openstack 7 1.8.11-1.el7ost
  • python-django-bash-completion openstack 7 1.8.11-1.el7ost
  • python-django openstack 5 1.6.11-5.el6ost
  • python-django-bash-completion openstack 5 1.6.11-5.el6ost

red hat advisories RHSA-2016:0506RHSA-2016:0503RHSA-2016:0504RHSA-2016:0505RHSA-2016:0502

  • python-Django openSUSE Tumbleweed 1.10.4-1.1

opensuse advisories openSUSE-SU-2024:10361-1

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-2016-2513 updated cvss 4.3

python-django: User enumeration through timing difference on password hasher work factor upgrade

  • Red Hat Ceph Storage 1.2 Django Red Hat Ceph Storage 1.3 Django
    affected: no fix planned “Will not fix”
  • Red Hat Subscription Asset Manager Django
    affected: no fix available
  • Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6 python-django 1.6.11-5.el6ost, python-django-bash-completion 1.6.11-5.el6ost
    fixed: vendor fix RHSA-2016:0502
  • Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7 python-django 1.6.11-5.el7ost, python-django-bash-completion 1.6.11-5.el7ost
    fixed: vendor fix RHSA-2016:0506
  • Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7 python-django 1.6.11-5.el7ost, python-django-bash-completion 1.6.11-5.el7ost
    fixed: vendor fix RHSA-2016:0505
  • Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 python-django 1.8.11-1.el7ost, python-django-bash-completion 1.8.11-1.el7ost
    fixed: vendor fix RHSA-2016:0504
  • Red Hat Enterprise Linux OpenStack Platform 7.0 Operational Tools for RHEL 7 python-django 1.6.11-5.el7ost, python-django-bash-completion 1.6.11-5.el7ost
    fixed: vendor fix RHSA-2016:0503
  • 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
    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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi django
<1.8.10
>=1.9, <1.9.3
1.8.10
1.9.3

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
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.