CVE-2016-9013
Critical
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.
SeverityCritical
CVSS9.8
Exploit probability—
Product
Django
PublishedDec 9, 2016
First seenDec 9, 2016
How to fix
Update
- django1.10.3, 1.9.11, 1.8.16 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| djangoproject django | 1.10, 1.10.1, 1.10.2, 1.9, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.10, 1.8, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.8.8, 1.8.9, 1.8.10, 1.8.11, 1.8.12, 1.8.13, 1.8.14, 1.8.15 | — |
| canonical ubuntu_linux | 12.04, 14.04, 16.04, 16.10 | — |
| fedoraproject fedora | 24, 25 | — |
| djangoPyPI | 1.10a1 ≤ v < 1.10.3, 1.9a1 ≤ v < 1.9.11, 1.8a1 ≤ v < 1.8.16, 1.8 ≤ v < 1.8.16, 1.9 ≤ v < 1.9.11, 1.10 ≤ v < 1.10.3 | 1.10.3, 1.9.11, 1.8.16 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.