Django user with hardcoded password created when running tests on Oracle
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
1.8.16Django 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.
From the CVE record · mitre
Affected Django versions use a hardcoded password for a temporary database user created when running tests with Oracle. A remote attacker may gain access to the database server if no password is manually specified in the database settings TEST dictionary.
Engineers using the PyPI django package in the 1.8, 1.9, or 1.10 release lines before 1.8.16, 1.9.11, or 1.10.3, respectively, should check their installations.