Severity
Severity not reported.
Affected versions
| Affected | Fixed in |
|---|---|
2.1 to before 2.1.10 | 2.1.10Advisories → |
2.2 to before 2.2.3 | 2.2.3Advisories → |
1.11 to before 1.11.22 | 1.11.22Advisories → |
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.
References
- Webgroups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ ↗
- ARTICLEwww.djangoproject.com/weblog/2019/jul/01/security-releases/ ↗
- Webdocs.djangoproject.com/en/dev/releases/security/ ↗
- Webwww.openwall.com/lists/oss-security/2019/07/01/3 ↗
- Webusn.ubuntu.com/4043-1/ ↗
- Webwww.securityfocus.com/bid/109018 ↗
- Advisorysecurity.netapp.com/advisory/ntap-20190705-0002/ ↗
- Advisorywww.debian.org/security/2019/dsa-4476 ↗
- Webseclists.org/bugtraq/2019/Jul/10 ↗
- Weblists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL/ ↗
- Weblists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html ↗
- Weblists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html ↗
- Advisorygithub.com/advisories/GHSA-6c7v-2f49-8h26 ↗