Description
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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-3835-1 | python-django security update |
EUVD |
EUVD-2016-0006 | 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. |
Github GHSA |
GHSA-mv8g-fhh6-6267 | Django user with hardcoded password created when running tests on Oracle |
Ubuntu USN |
USN-3115-1 | Django vulnerabilities |
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-06T02:35:02.828Z
Reserved: 2016-10-25T00:00:00.000Z
Link: CVE-2016-9013
No data.
Status : Deferred
Published: 2016-12-09T20:59:05.657
Modified: 2025-04-12T10:46:40.837
Link: CVE-2016-9013
OpenCVE Enrichment
No data.
Weaknesses
Debian DSA
EUVD
Github GHSA
Ubuntu USN