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.
References
Link | Resource |
---|---|
http://www.debian.org/security/2017/dsa-3835 | |
http://www.securityfocus.com/bid/94069 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1037159 | Third Party Advisory VDB Entry |
http://www.ubuntu.com/usn/USN-3115-1 | Third Party Advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OG5ROMUPS6C7BXELD3TAUUH7OBYV56WQ/ | |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QXDKJYHN74BWY3P7AR2UZDVJREQMRE6S/ | |
https://www.djangoproject.com/weblog/2016/nov/01/security-releases/ | Release Notes Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
History
No history.
Information
Published : 2016-12-09 20:59
Updated : 2023-11-07 02:36
NVD link : CVE-2016-9013
Mitre link : CVE-2016-9013
CVE.ORG link : CVE-2016-9013
JSON object : View
Products Affected
djangoproject
- django
canonical
- ubuntu_linux
fedoraproject
- fedora
CWE
CWE-798
Use of Hard-coded Credentials