CVE-2017-7234: Medium severity djangoproject Django vulnerability

Published Apr 4, 2017
·
Updated

A maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the django.views.static.serve() view could redirect to any other domain, aka an open redirect vulnerability.

Other sources

A maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the django.views.static.serve() view could redirect to any other domain, aka an open redirect vulnerability.

Affected Software

75 affected componentsFixes available
pip/django>=1.8<1.8.18
1.8.18
pip/django>=1.9<1.9.13
1.9.13
pip/django>=1.10<1.10.7
1.10.7
djangoproject Django=1.8.0
djangoproject Django=1.8.0-a1
djangoproject Django=1.8.0-b1
djangoproject Django=1.8.0-b2
djangoproject Django=1.8.0-c1
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
djangoproject Django=1.8.16
djangoproject Django=1.8.17
djangoproject Django=1.9
djangoproject Django=1.9-a1
djangoproject Django=1.9-b1
djangoproject Django=1.9-rc1
djangoproject Django=1.9-rc2
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.9.11
djangoproject Django=1.9.12
djangoproject Django=1.10.0
djangoproject Django=1.10.0-a1
djangoproject Django=1.10.0-b1
djangoproject Django=1.10.0-rc1
djangoproject Django=1.10.1
djangoproject Django=1.10.2
djangoproject Django=1.10.3
djangoproject Django=1.10.4
djangoproject Django=1.10.5
djangoproject Django=1.10.6
alpine/py-django<1.10.7-r0
1.10.7-r0
alpine/py-django<1.8.18-r0
1.8.18-r0
alpine/py-django<1.8.18-r0
1.8.18-r0
alpine/py-django<1.8.18-r0
1.8.18-r0
alpine/py-django<1.8.18-r0
1.8.18-r0
alpine/py-django<1.10.7-r0
1.10.7-r0
alpine/py-django<1.10.7-r0
1.10.7-r0
alpine/py-django<1.10.7-r0
1.10.7-r0
alpine/py-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0
alpine/py3-django<1.10.7-r0
1.10.7-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 1.8.18
  2. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 1.9.13
  3. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 1.10.7
  4. Upgrade

    Upgrade alpine/py-django to a version that resolves this vulnerability.

    Fixed in 1.10.7-r0
  5. Upgrade

    Upgrade alpine/py-django to a version that resolves this vulnerability.

    Fixed in 1.8.18-r0
  6. Upgrade

    Upgrade alpine/py3-django to a version that resolves this vulnerability.

    Fixed in 1.10.7-r0

Event History

Apr 4, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:59 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·05:59 PM
DescriptionSeverityAffected Software
Jan 4, 2019
Advisory Published
via GitHub·05:50 PM

Frequently Asked Questions

1

What is the severity of CVE-2017-7234?

CVE-2017-7234 is classified as a medium severity vulnerability due to the potential for open redirects.

2

How do I fix CVE-2017-7234?

To remediate CVE-2017-7234, upgrade Django to version 1.10.7, 1.9.13, or 1.8.18 or later.

3

Which versions of Django are affected by CVE-2017-7234?

CVE-2017-7234 affects Django versions 1.10 prior to 1.10.7, 1.9 prior to 1.9.13, and 1.8 prior to 1.8.18.

4

What types of attacks could exploit CVE-2017-7234?

An attacker could exploit CVE-2017-7234 to redirect users to potentially malicious external websites.

5

Is there a workaround for CVE-2017-7234 until I can upgrade?

To mitigate CVE-2017-7234, consider disabling the use of django.views.static.serve() or implementing strict validation on redirect URLs.

Company

Resources

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203