GoogleOSV:PYSEC-2019-10PYSEC-2019-10
5.3 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.006 Low
EPSS
Percentile
78.3%
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
lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html
lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html
www.openwall.com/lists/oss-security/2019/07/01/3
www.securityfocus.com/bid/109018
docs.djangoproject.com/en/dev/releases/security/
github.com/advisories/GHSA-6c7v-2f49-8h26
groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ
lists.fedoraproject.org/archives/list/[email protected]/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL/
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/
Related
5.3 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.006 Low
EPSS
Percentile
78.3%