Django user with hardcoded password created when running tests on Oracle
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-9013US | critical9.8OT elevated | — | ||
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,… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.debian.org/security/2017/dsa-3835WEB
- http://www.ubuntu.com/usn/USN-3115-1WEB
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/34e10720d81b8d407aa14d763b6a7fe8f13b4f2eWEB
- https://github.com/django/django/commit/4844d86c7728c1a5a3bbce4ad336a8d32304072bWEB
- https://github.com/django/django/commit/70f99952965a430daf69eeb9947079aae535d2d0WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2016-17.yamlWEB
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OG5ROMUPS6C7BXELD3TAUUH7OBYV56WQWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan