Use of Hard-coded Credentials Affecting python-django package, versions <1:1.10.3-1


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
1.29% (87th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-PYTHONDJANGO-360976
  • published9 Dec 2016
  • disclosed9 Dec 2016

Introduced: 9 Dec 2016

CVE-2016-9013  (opens in a new tab)
CWE-798  (opens in a new tab)

How to fix?

Upgrade Debian:unstable python-django to version 1:1.10.3-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-django package and not the python-django package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.