# CVE-2017-7233: Django open redirect and possible XSS attack via user-supplied numeric redirect URLs > Django's URL safety check incorrectly validates numeric URLs, allowing open redirects and potential XSS attacks if developers rely on the flawed function. - **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **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:** Yes - **Published:** 4 Apr 2017 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2017-7233, DEBIAN-CVE-2017-7233, GHSA-37hp-765x-j95x, PYSEC-2017-9, RHSA-2017:1445, RHSA-2017:1451, RHSA-2017:1462, RHSA-2017:1470, RHSA-2017:1596, RHSA-2017:3093, UBUNTU-CVE-2017-7233 ## 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 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2017-7233? 7 open source packages ship an affected version, including django and Django. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `django` | PyPI | From 1.10 | 1.10.7, 1.9.13, 1.8.18 | | `django` | PyPI | From 1.10a1 | 1.10.7 | | `django` | PyPI | From 1.8a1 | 1.8.18 | | `django` | PyPI | From 1.9a1 | 1.9.13 | | `Django` | PyPI | From 1.10a1 | 1.10.7 | | `Django` | PyPI | From 1.8a1 | 1.8.18 | | `Django` | PyPI | From 1.9a1 | 1.9.13 | | `python-django` | Red Hat:openstack:10::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django-bash-completion` | Red Hat:openstack:10::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django` | Red Hat:openstack:11::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django-bash-completion` | Red Hat:openstack:11::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django` | Red Hat:openstack:6::el7 | All versions | 0:1.6.11-7.el7ost | | `python-django-bash-completion` | Red Hat:openstack:6::el7 | All versions | 0:1.6.11-7.el7ost | | `python-django-doc` | Red Hat:openstack:6::el7 | All versions | 0:1.6.11-7.el7ost | | `python-django` | Red Hat:openstack:7::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django-bash-completion` | Red Hat:openstack:7::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django-doc` | Red Hat:openstack:7::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django` | Red Hat:openstack:8::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django-bash-completion` | Red Hat:openstack:8::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django` | Red Hat:openstack:9::el7 | All versions | 0:1.8.18-1.el7ost | | `python-django-bash-completion` | Red Hat:openstack:9::el7 | All versions | 0:1.8.18-1.el7ost | Products: 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. ## Other vulnerabilities in Djangoproject Django - [CVE-2026-4277](https://insights.sbomify.com/CVE-2026-4277/): Privilege abuse in GenericInlineModelAdmin (critical 9.8) - [CVE-2024-53908](https://insights.sbomify.com/CVE-2024-53908/): Django SQL injection in HasKey(lhs, rhs) on Oracle (critical 9.8) - [CVE-2024-42005](https://insights.sbomify.com/CVE-2024-42005/): Django SQL injection vulnerability (critical 9.8) - [CVE-2023-31047](https://insights.sbomify.com/CVE-2023-31047/): Django bypasses validation when using one form field to upload multiple files (critical 9.8) - [CVE-2022-34265](https://insights.sbomify.com/CVE-2022-34265/): Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-7233 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2017-7233 in the wild and no public exploit code. Affected packages and fixed versions: - django (PyPI): affected from 1.10; fixed in 1.10.7, 1.9.13, 1.8.18 - django (PyPI): affected from 1.10a1; fixed in 1.10.7 - django (PyPI): affected from 1.8a1; fixed in 1.8.18 - django (PyPI): affected from 1.9a1; fixed in 1.9.13 - Django (PyPI): affected from 1.10a1; fixed in 1.10.7 - Django (PyPI): affected from 1.8a1; fixed in 1.8.18 - Django (PyPI): affected from 1.9a1; fixed in 1.9.13 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-7233/ (Markdown: https://insights.sbomify.com/CVE-2017-7233/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7233 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7233 - OSV: https://osv.dev/vulnerability/CVE-2017-7233 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7233/ Summaries are generated and may contain mistakes; the official description above is the record.