Vulnerability in Djangoproject Django
CVE-2019-12781
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
EPSS exploit prediction
EPSS 0.017, 77.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Djangoproject Django
- Canonical Ubuntu Linux — versions 16.04, 18.04, 18.10
- Debian Linux — versions 9.0
Weakness classification (CWE)
References
- docs.djangoproject.com/en/dev/releases/security/ (Patch, Vendor Advisory)
- groups.google.com/forum/
- www.djangoproject.com/weblog/2019/jul/01/security-releases/ (Patch, Vendor Advisory)
- [oss-security] 20190701 Django: CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS (mailing-list, Patch, Mailing List, Third Party Advisory)
- USN-4043-1 (vendor-advisory, Third Party Advisory)
- www.securityfocus.com/bid/109018 (Third Party Advisory, vdb-entry)
- security.netapp.com/advisory/ntap-20190705-0002/ (Third Party Advisory)
- DSA-4476 (vendor-advisory, Third Party Advisory)
- 20190708 [SECURITY] [DSA 4476-1] python-django security update (mailing-list, Third Party Advisory)
- FEDORA-2019-d9aa58d863 (vendor-advisory)