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 acces…

EPSS: 0.012 (79.5th percentile) — read the EPSS interpretation.

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.

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

  • cve@mitre.org (x_refsource_CONFIRM, Release Notes, Vendor Advisory)
  • FEDORA-2016-d4571bf555 (x_refsource_FEDORA, vendor-advisory)
  • DSA-3835 (vendor-advisory, x_refsource_DEBIAN)
  • USN-3115-1 (x_refsource_UBUNTU, vendor-advisory, Third Party Advisory)
  • 94069 (Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID)
  • 1037159 (Third Party Advisory, VDB Entry, vdb-entry, x_refsource_SECTRACK)
  • FEDORA-2016-3eb5a55123 (x_refsource_FEDORA, vendor-advisory)

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.