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.
Remediation
References
Related Vulnerabilities
WordPress Plugin Rockhoist Badges Cross-Site Scripting (1.2.2)
WordPress Plugin Ultimate Addons for Elementor Security Bypass (1.20.0)
Joomla Cross-Site Request Forgery (CSRF) Vulnerability (CVE-2020-15700)
Moodle Improper Input Validation Vulnerability (CVE-2012-1168)
Internet Information Services Other Vulnerability (CVE-2000-0304)