Safety vulnerability ID: 37261
The information on this page was manually curated by our Cybersecurity Intelligence Team.
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.
Latest version: 5.0.4
A high-level Python web framework that encourages rapid development and clean, pragmatic design.
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.
CONFIRM:https://www.djangoproject.com/weblog/2019/jul/01/security-releases/: https://www.djangoproject.com/weblog/2019/jul/01/security-releases/
MISC:https://docs.djangoproject.com/en/dev/releases/security/: https://docs.djangoproject.com/en/dev/releases/security/
MISC:https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ: https://groups.google.com/forum/#%21topic/django-announce/Is4kLY9ZcZQ
MLIST:[oss-security] 20190701 Django: CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS: http://www.openwall.com/lists/oss-security/2019/07/01/3
UBUNTU:USN-4043-1: https://usn.ubuntu.com/4043-1/
Scan your Python project for dependency vulnerabilities in two minutes
Scan your application