An HTTP detection flaw was discovered in Django. If deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme() incorrectly detected client requests made using HTTP as using HTTPS. This resulted in incorrect results for is_secure() and build_absolute_uri(), and HTTP requests were not correctly redirected to HTTPS in accordance with SECURE_SSL_REDIRECT.
0:1.11.27-1.el7ost0:2.1.11-1.el8ost0:1.3.0-1.el7sat0:1.4.6-1.el7ar0:0.0.5-1.el7sat0:1.7.1-1.el7sat0:0.6.13-1.el7sat0:3.1.21-1.el7sat0:0.7.4-1.el7satExploitability
AV:NAC:HPR:NUI:NScope
S:UImpact
C:LI:LA:N4.8/CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N