Vulnerabilities · 2019 · Djangoproject
CVE-2019-12781
Djangoproject Django vulnerability
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.
Affected products
Django, Ubuntu Linux, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.djangoproject.com/en/dev/releases/security/ · Patch
- www.djangoproject.com/weblog/2019/jul/01/security-releases/ · Patch
- www.openwall.com/lists/oss-security/2019/07/01/3 · Patch
- www.securityfocus.com/bid/109018 · Third Party Advisory
- seclists.org/bugtraq/2019/Jul/10 · Third Party Advisory
- security.netapp.com/advisory/ntap-20190705-0002/ · Third Party Advisory
- usn.ubuntu.com/4043-1/ · Third Party Advisory
- www.debian.org/security/2019/dsa-4476 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-12781
- cve.org/CVERecord?id=CVE-2019-12781
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.