PRIOn knowledge basePRION:CVE-2019-12781Design/Logic Flaw
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.
| CPE | Name | Operator | Version |
|---|---|---|---|
| ubuntu_linux | eq | 16.04 | |
| ubuntu_linux | eq | 18.04 | |
| ubuntu_linux | eq | 18.10 | |
| ubuntu_linux | eq | 19.04 | |
| debian_linux | eq | 9.0 | |
| django | ge | 1.11 | |
| django | lt | 1.11.22 | |
| django | ge | 2.1 | |
| django | lt | 2.1.10 | |
| django | ge | 2.2 |
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/
groups.google.com/forum/
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
