CVE-2017-7233 Django open redirect and possible XSS attack via user-supplied numeric redirect URLs

Medium 6.1 Published Updated

Django's URL safety check incorrectly validates numeric URLs, allowing open redirects and potential XSS attacks if developers rely on the flawed function.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2017-7233?

CVE-2017-7233 is a medium-severity vulnerability in Djangoproject Django, published on 4 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

Django 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an "on success" URL. The security check for these redirects (namely ``django.utils.http.is_safe_url()``) considered some numeric URLs "safe" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on ``is_safe_url()`` to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.

Weakness: CWE-601

Which versions are affected by CVE-2017-7233?

7 open source packages ship an affected version, including django and Django. It affects 1 product.

PackageAffectedFixed in
django PyPIFrom 1.101.10.7, 1.9.13, 1.8.18
django PyPIFrom 1.10a11.10.7
django PyPIFrom 1.8a11.8.18
django PyPIFrom 1.9a11.9.13
Django PyPIFrom 1.10a11.10.7
Django PyPIFrom 1.8a11.8.18
1 more packages
Django PyPIFrom 1.9a11.9.13
Linux distribution packages (14)
python-django Red Hat:openstack:10::el7All versions0:1.8.18-1.el7ost
python-django-bash-completion Red Hat:openstack:10::el7All versions0:1.8.18-1.el7ost
python-django Red Hat:openstack:11::el7All versions0:1.8.18-1.el7ost
python-django-bash-completion Red Hat:openstack:11::el7All versions0:1.8.18-1.el7ost
python-django Red Hat:openstack:6::el7All versions0:1.6.11-7.el7ost
python-django-bash-completion Red Hat:openstack:6::el7All versions0:1.6.11-7.el7ost
python-django-doc Red Hat:openstack:6::el7All versions0:1.6.11-7.el7ost
python-django Red Hat:openstack:7::el7All versions0:1.8.18-1.el7ost
python-django-bash-completion Red Hat:openstack:7::el7All versions0:1.8.18-1.el7ost
python-django-doc Red Hat:openstack:7::el7All versions0:1.8.18-1.el7ost
python-django Red Hat:openstack:8::el7All versions0:1.8.18-1.el7ost
python-django-bash-completion Red Hat:openstack:8::el7All versions0:1.8.18-1.el7ost
python-django Red Hat:openstack:9::el7All versions0:1.8.18-1.el7ost
python-django-bash-completion Red Hat:openstack:9::el7All versions0:1.8.18-1.el7ost

Products include Djangoproject Django.

How do I fix CVE-2017-7233?

Upgrade django to a fixed version for your release line: 1.10.7, 1.9.13 or 1.8.18.

Is CVE-2017-7233 being exploited?

There is no known exploitation of CVE-2017-7233 in the wild and no public exploit code.

All Djangoproject Django vulnerabilities

Sources

Also known as ALPINE-CVE-2017-7233, DEBIAN-CVE-2017-7233, GHSA-37hp-765x-j95x, PYSEC-2017-9, RHSA-2017:1445, RHSA-2017:1451 and 5 more.

Is CVE-2017-7233 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free