Severity
- CVSS 3.x
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| e3c9412d86c3c394e2604e63f3b51c102ae3e3d7 through 320ec4ed27c254a87e09a70601b1b27ae0a0456e | No fix listed |
Also listed as affected (38)
| |
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.
References
- Webwww.securitytracker.com/id/1038177 ↗
- Advisorywww.debian.org/security/2017/dsa-3835 ↗
- Advisorywww.securityfocus.com/bid/97406 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2017:1445 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2017:1451 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2017:1462 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2017:1470 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2017:1596 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2017:3093 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2018:2927 ↗
- Advisorywww.djangoproject.com/weblog/2017/apr/04/security-releases/ ↗