Back to search
CVE-2019-12781
Published: Jul 1, 2019
Modified: Aug 4, 2024
PUBLISHED
Description
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.
| Vendor | Product | Versions |
|---|---|---|
n/a | n/a | affected n/a |
References
https://docs.djangoproject.com/en/dev/releases/security/
x_refsource_MISC
https://www.djangoproject.com/weblog/2019/jul/01/security-releases/
x_refsource_CONFIRM
[oss-security] 20190701 Django: CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS
mailing-list
x_refsource_MLIST
USN-4043-1
vendor-advisory
x_refsource_UBUNTU
109018
vdb-entry
x_refsource_BID
https://security.netapp.com/advisory/ntap-20190705-0002/
x_refsource_CONFIRM
DSA-4476
vendor-advisory
x_refsource_DEBIAN
20190708 [SECURITY] [DSA 4476-1] python-django security update
mailing-list
x_refsource_BUGTRAQ
FEDORA-2019-d9aa58d863
vendor-advisory
x_refsource_FEDORA
openSUSE-SU-2019:1839
vendor-advisory
x_refsource_SUSE
openSUSE-SU-2019:1872
vendor-advisory
x_refsource_SUSE
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now