CVE-2019-12781
Medium
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.
SeverityMedium
CVSS5.3
Exploit probability—
Product
Django
PublishedJul 1, 2019
First seenJul 1, 2019
How to fix
Update
- djangoproject django1.11.22, 2.1.10, 2.2.3 or later
- django2.1.10, 2.2.3, 1.11.22 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| djangoproject django | 1.11 ≤ v < 1.11.22, 2.1 ≤ v < 2.1.10, 2.2 ≤ v < 2.2.3 | 1.11.22, 2.1.10, 2.2.3 |
| canonical ubuntu_linux | 16.04, 18.04, 18.10, 19.04 | — |
| debian debian_linux | 9.0 | — |
| djangoPyPI | 2.1 ≤ v < 2.1.10, 2.2 ≤ v < 2.2.3, 1.11 ≤ v < 1.11.22 | 2.1.10, 2.2.3, 1.11.22 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.