Vulnerability advisory

GHSA-6c7v-2f49-8h26

Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS

Published Jul 3, 2019Updated Sep 18, 2024OSV record ↗

Also known as CVE-2019-12781PYSEC-2019-10

Severity

CVSS 3.xCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Affected versions

django PyPI

All django advisories →

Affected	Fixed in
`2.1` to before 2.1.10	`2.1.10`Advisories →
Also listed as affected (9) `2.1` `2.1.1` `2.1.2` `2.1.3` `2.1.4` `2.1.5` `2.1.7` `2.1.8` `2.1.9`
`2.2` to before 2.2.3	`2.2.3`Advisories →
Also listed as affected (3) `2.2` `2.2.1` `2.2.2`
`1.11` to before 1.11.22	`1.11.22`Advisories →
Also listed as affected (21) `1.11` `1.11.1` `1.11.10` `1.11.11` `1.11.12` `1.11.13` `1.11.14` `1.11.15` `1.11.16` `1.11.17` `1.11.18` `1.11.2` `1.11.20` `1.11.21` `1.11.3` `1.11.4` `1.11.5` `1.11.6` `1.11.7` `1.11.8` `1.11.9`

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.

GHSA-6c7v-2f49-8h26

Affected versions

django PyPI

Description

References