Skip to content
Fencer Intel
critical 9.8

CVE-2016-9013 in the critical feed json

Django user with hardcoded password created when running tests on Oracle

published 2016-12-09 9 y ago modified 2026-06-17 4 mo ago also GHSA-mv8g-fhh6-6267 , PYSEC-2016-17 , EUVD-2016-0006

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

Summary

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.

Patch / fix

  • pypi django 1.8.16, 1.9.11, 1.10.3
  • python-django Debian 14, Debian 13, Debian 12 1:1.10.3-1

debian advisories DEBIAN-CVE-2016-9013

  • python-django Ubuntu 14.04 LTS 1.6.1-2ubuntu0.16
  • python-django Ubuntu 16.04 LTS 1.8.7-1ubuntu5.4

ubuntu advisories UBUNTU-CVE-2016-9013

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 Cloud 6 1.8.19-3.6.1
  • python-Django OpenStack Cloud 7 1.8.19-3.4.1

suse advisories SUSE-SU-2018:1102-1SUSE-SU-2018:0973-1

  • py-django Alpine 3.10, Alpine 3.9, Alpine 3.8 +6 more 1.8.16-r0
  • py3-django Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 1.8.16-r0

alpine advisories ALPINE-CVE-2016-9013

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-django Arch Linux 1.10.3-1

arch linux advisories AVG-57

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-9013 updated cvss 7.4

python-django: user with hardcoded password created when running tests on Oracle

  • Red Hat Subscription Asset Manager Django
    affected: no fix planned “Will not fix”
  • Red Hat Ceph Storage 1.3 Django Red Hat Ceph Storage 2 python-django, python-django-bash-completion Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) python-django Red Hat Enterprise Linux OpenStack Platform 6 (Juno) 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
    +7 more products
    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 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 10 (Newton) Operational Tools python-django, python-django-bash-completion Red Hat Storage Console 2 Django, 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi django
>=1.10a1, <1.10.3
>=1.9a1, <1.9.11
>=1.8a1, <1.8.16
>=1.8, <1.8.16
>=1.9, <1.9.11
>=1.10, <1.10.3
1.10.3
1.9.11
1.8.16

Classification

Weakness
  • CWE-798 Use of Hard-coded 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.