Vulnerability in Djangoproject Django

CVE-2016-9013

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.052 (92.2th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 92nd percentile — 92.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2016-9013: held from 0.052 to 0.052.

EPSS over last 30 days · oldest: 0.052 · newest: 0.052 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2016-9013?
CVE-2016-9013 is a critical-severity vulnerability in Djangoproject Django, classified under Use of Hard-coded Credentials. CVSS score: 9.8/10. Published 2016-12-09.
How severe is CVE-2016-9013?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2016-9013 known to be exploited?
2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.