Summary
This update for python-Django fixes the following issues:
Security issues fixed:
- CVE-2018-7537: Fixed catastrophic backtracking in django.utils.text.Truncator. (bsc#1083305)
- CVE-2018-7536: Fixed catastrophic backtracking in urlize and urlizetrunc template filters. (bsc#1083304)
- CVE-2017-12794: Fixed XSS possibility in traceback section of technical 500 debug page (bsc#1056284)
- CVE-2017-7234: Open redirect vulnerability in django.views.static.serve() (bsc#1031451)
- CVE-2017-7233: Open redirect and possible XSS attack via user-supplied numeric redirect URLs (bsc#1031450)
- CVE-2016-9014: DNS rebinding vulnerability when DEBUG=True (bsc#1008047)
- CVE-2016-9013: User with hardcoded password created when running tests on Oracle (bsc#1008050)
- CVE-2016-7401: CSRF protection bypass on a site with Google Analytics (bsc#1001374)
- CVE-2016-2512: Vulnerability in the function tils.http.is_safe_url could allow remote users to arbitrary
web site and conduct phishing attacks. (bsc#bnc#967999)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · OpenStack Cloud 6 | python-Django | 1.8.19-3.6.1 |
Vulnerabilities 9
-
Critical 9.8
Django user with hardcoded password created when running tests on Oracle
Django 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 use a hardcoded password for a temporary database user created when running tests with an Oracle database, which makes it easier for remote attackers to obtain access to the database se…
-
High 8.1
Django DNS Rebinding Vulnerability
Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host header against settings.ALLOWED_HOSTS.
-
High 7.5
Django CSRF Protection Bypass
The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.
-
High 7.4
Django XSS Vulnerability
The utils.http.is_safe_url function in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks or possibly conduct cross-site scripting (XSS) attacks via a URL containing basic …
-
Medium 6.1
Django vulnerable to XSS on 500 pages
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affe…
-
Medium 6.1
Django open redirect and possible XSS attack via user-supplied numeric redirect URLs
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 URL…
-
Medium 6.1
Django open redirect
A maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the ``django.views.static.serve()`` view could redirect to any other domain, aka an open redirect vulnerability.
-
Medium 5.3
Django denial-of-service possibility in urlize and urlizetrunc template filters
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (…
-
Medium 5.3
Django Denial-of-service possibility in truncatechars_html and truncatewords_html template filters
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catas…
References
-
report
https://bugzilla.suse.com/1001374
-
report
https://bugzilla.suse.com/1008047
-
report
https://bugzilla.suse.com/1008050
-
report
https://bugzilla.suse.com/1031450
-
report
https://bugzilla.suse.com/1031451
-
report
https://bugzilla.suse.com/1056284
-
report
https://bugzilla.suse.com/1083304
-
report
https://bugzilla.suse.com/1083305
-
report
https://bugzilla.suse.com/967999
-
web
https://www.suse.com/security/cve/CVE-2016-2512
-
web
https://www.suse.com/security/cve/CVE-2016-7401
-
web
https://www.suse.com/security/cve/CVE-2016-9013
-
web
https://www.suse.com/security/cve/CVE-2016-9014
-
web
https://www.suse.com/security/cve/CVE-2017-12794
-
web
https://www.suse.com/security/cve/CVE-2017-7233
-
web
https://www.suse.com/security/cve/CVE-2017-7234
-
web
https://www.suse.com/security/cve/CVE-2018-7536
-
web
https://www.suse.com/security/cve/CVE-2018-7537