django
Affected
- introduced
2.1, fixed2.1.10(ecosystem)
Fixed versions
2.1.10
Fix
- Fixed version
2.1.10pip install --upgrade django==2.1.10
Advisory
Also known as: CVE-2019-12781, PYSEC-2019-10
Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS
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.
Medium Basis: The source's own band: MODERATE
2.1, fixed 2.1.10 (ecosystem)2.1.10
2.1.10pip install --upgrade django==2.1.102.2, fixed 2.2.3 (ecosystem)2.2.3
2.2.3pip install --upgrade django==2.2.31.11, fixed 1.11.22 (ecosystem)1.11.22
1.11.22pip install --upgrade django==1.11.22Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0