The following flaw was reported in Django: When running tests with an Oracle database, Django creates a temporary database user. In older versions, if a password isn't manually specified in the database settings 'TEST' dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the 'manage.py test --keepdb' option or if the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run.
Acknowledgments: Name: the Django project
Created attachment 1214631 [details] oracle-1.10.x.diff
Created attachment 1214632 [details] oracle-1.8.x.diff
Created attachment 1214633 [details] oracle-1.9.x.diff
Created attachment 1214634 [details] oracle-master.diff
Public via: https://www.djangoproject.com/weblog/2016/nov/01/security-releases/
Created Django14 tracking bugs for this issue: Affects: epel-6 [bug 1390685]
Created python-django tracking bugs for this issue: Affects: fedora-all [bug 1390684]
Created python-django tracking bugs for this issue: Affects: epel-7 [bug 1390687]