CVE-2019-12781: Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS
(updated )
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.
References
- docs.djangoproject.com/en/dev/releases/security
- github.com/advisories/GHSA-6c7v-2f49-8h26
- github.com/django/django
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2019-10.yaml
- groups.google.com/forum/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL
- nvd.nist.gov/vuln/detail/CVE-2019-12781
- seclists.org/bugtraq/2019/Jul/10
- security.netapp.com/advisory/ntap-20190705-0002
- usn.ubuntu.com/4043-1
- www.debian.org/security/2019/dsa-4476
- www.djangoproject.com/weblog/2019/jul/01/security-releases
Detect and mitigate CVE-2019-12781 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →