CWE
798
Advisory Published
Advisory Published
Updated

CVE-2016-9013

First published: Fri Dec 09 2016(Updated: )

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.

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
pip/Django>=1.8a1<1.8.16
1.8.16
pip/Django>=1.9a1<1.9.11
1.9.11
pip/Django>=1.10a1<1.10.3
1.10.3
djangoproject Django=1.10
djangoproject Django=1.10.1
djangoproject Django=1.10.2
Ubuntu=12.04
Ubuntu=14.04
Ubuntu=16.04
Ubuntu=16.10
djangoproject Django=1.9
djangoproject Django=1.9.1
djangoproject Django=1.9.2
djangoproject Django=1.9.3
djangoproject Django=1.9.4
djangoproject Django=1.9.5
djangoproject Django=1.9.6
djangoproject Django=1.9.7
djangoproject Django=1.9.8
djangoproject Django=1.9.9
djangoproject Django=1.9.10
djangoproject Django=1.8
djangoproject Django=1.8.1
djangoproject Django=1.8.2
djangoproject Django=1.8.3
djangoproject Django=1.8.4
djangoproject Django=1.8.5
djangoproject Django=1.8.6
djangoproject Django=1.8.7
djangoproject Django=1.8.8
djangoproject Django=1.8.9
djangoproject Django=1.8.10
djangoproject Django=1.8.11
djangoproject Django=1.8.12
djangoproject Django=1.8.13
djangoproject Django=1.8.14
djangoproject Django=1.8.15
Fedora=24
Fedora=25

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-9013?

    CVE-2016-9013 is considered a moderate severity vulnerability due to the potential for unauthorized database access.

  • How do I fix CVE-2016-9013?

    To fix CVE-2016-9013, upgrade Django to version 1.8.16, 1.9.11, or 1.10.3 or later.

  • What versions of Django are affected by CVE-2016-9013?

    Django versions 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 are affected by CVE-2016-9013.

  • What type of attack can exploit CVE-2016-9013?

    CVE-2016-9013 can be exploited by remote attackers to gain unauthorized access to the Oracle database.

  • Is CVE-2016-9013 specific to any database type?

    Yes, CVE-2016-9013 specifically involves a vulnerability in Django when used with an Oracle database.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203