Django open redirect and possible XSS attack via user-supplied numeric redirect URLs
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
1.8.18Django 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.
From the CVE record · mitre
Django's redirect safety check incorrectly treats some numeric URLs as safe when they are not. An attacker can use a crafted URL to redirect a user; XSS is also possible if a developer uses the check to validate a URL placed in a link.
Teams running the PyPI django package in the 1.8, 1.9, or 1.10 series before 1.8.18, 1.9.13, or 1.10.7, respectively, should check their deployments.