https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:30:22 +0000 https://cve.radiocsirt.org/vuln/bdu:2019-02513 bdu:2019-02513 https://cve.radiocsirt.org/vuln/bdu:2019-02513 https://cve.radiocsirt.org/vuln/cnvd-2019-21074 cnvd-2019-21074 https://cve.radiocsirt.org/vuln/cnvd-2019-21074 https://cve.radiocsirt.org/vuln/euvd-2026-55220 EUVD-2026-55220 https://cve.radiocsirt.org/vuln/euvd-2026-55220 https://cve.radiocsirt.org/vuln/fkie_cve-2019-12781 <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-12781 https://cve.radiocsirt.org/vuln/ghsa-6c7v-2f49-8h26 <p><strong>Affected:</strong> PyPI: Django</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> <p><strong>Affected:</strong> PyPI: Django</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> https://cve.radiocsirt.org/vuln/ghsa-6c7v-2f49-8h26 https://cve.radiocsirt.org/vuln/gsd-2019-12781 gsd-2019-12781 https://cve.radiocsirt.org/vuln/gsd-2019-12781 https://cve.radiocsirt.org/vuln/opensuse-su-2019:1839-1 <p>Security update for python-Django</p> <p>Security update for python-Django</p> https://cve.radiocsirt.org/vuln/opensuse-su-2019:1839-1 https://cve.radiocsirt.org/vuln/pysec-2019-10 <p><strong>Affected:</strong> PyPI: django</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> <p><strong>Affected:</strong> PyPI: django</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> https://cve.radiocsirt.org/vuln/pysec-2019-10 https://cve.radiocsirt.org/vuln/rhsa-2020:1324 <p>Django: Incorrect HTTP detection with reverse-proxy connecting via HTTPS Django: backtracking in a regular expression in django.utils.text.Truncator leads to DoS Django: the behavior of the underlying HTMLParser leading to DoS Django: SQL injection possibility in key and index lookups for JSONField/HStoreField Django: Potential memory exhaustion in django.utils.encoding.uri_to_iri()</p> <p>Django: Incorrect HTTP detection with reverse-proxy connecting via HTTPS Django: backtracking in a regular expression in django.utils.text.Truncator leads to DoS Django: the behavior of the underlying HTMLParser leading to DoS Django: SQL injection possibility in key and index lookups for JSONField/HStoreField Django: Potential memory exhaustion in django.utils.encoding.uri_to_iri()</p> https://cve.radiocsirt.org/vuln/rhsa-2020:1324 https://cve.radiocsirt.org/vuln/suse-su-2019:2257-1 <p>Security update for python-Django</p> <p>Security update for python-Django</p> https://cve.radiocsirt.org/vuln/suse-su-2019:2257-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-12781 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: python-django, Ubuntu:16.04:LTS: python-django, Ubuntu:18.04:LTS: python-django</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: python-django, Ubuntu:16.04:LTS: python-django, Ubuntu:18.04:LTS: python-django</p> <p>An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-12781