—
PYSEC-2019-10
Quick fix
PYSEC-2019-10 — django: upgrade to the fixed version with the command below.
pip install --upgrade 'django>=1.11.22'Details
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.
Are you affected?
Enter the version of the package you're using.
Affected packages
References
- https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ[WEB]
- https://www.djangoproject.com/weblog/2019/jul/01/security-releases/[ARTICLE]
- https://docs.djangoproject.com/en/dev/releases/security/[WEB]
- http://www.openwall.com/lists/oss-security/2019/07/01/3[WEB]
- https://usn.ubuntu.com/4043-1/[WEB]
- http://www.securityfocus.com/bid/109018[WEB]
- https://security.netapp.com/advisory/ntap-20190705-0002/[ADVISORY]
- https://www.debian.org/security/2019/dsa-4476[ADVISORY]
- https://seclists.org/bugtraq/2019/Jul/10[WEB]
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL/[WEB]
- http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html[WEB]
- http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html[WEB]
- https://github.com/advisories/GHSA-6c7v-2f49-8h26[ADVISORY]