Open Redirect in Djangoproject Django
CVE-2017-7233
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.
Vulnerability class: Open Redirect
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.1 (Medium). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N.
EPSS exploit prediction
EPSS 0.024, 84.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Djangoproject Django — versions 1.8.0, 1.8.1, 1.8.2
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (Crossroadsman/treehouse-techdegree-python-project9, leoChristofoli/CRUD-170406). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- www.securitytracker.com/id/1038177 (vdb-entry)
- RHSA-2017:1596 (vendor-advisory)
- www.securityfocus.com/bid/97406 (Third Party Advisory, VDB Entry, vdb-entry)
- RHSA-2017:3093 (vendor-advisory)
- DSA-3835 (vendor-advisory)
- RHSA-2017:1445 (vendor-advisory)
- RHSA-2017:1451 (vendor-advisory)
- RHSA-2018:2927 (vendor-advisory)
- RHSA-2017:1470 (vendor-advisory)
- www.djangoproject.com/weblog/2017/apr/04/security-releases/ (Vendor Advisory)