GitHub Advisoryadvisory · PyPI

GHSA-6c7v-2f49-8h26 Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS

MEDIUM Published 2019-07-03 Modified 2024-09-18 Official page ↗
Aliases
CVE-2019-12781
Ecosystem
PyPI
Packages
Django
Severity
Moderate
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-319
Reviewed
2019-07-03

Affected packages

• PyPI Django: >= 2.1, < 2.1.10 → fixed in 2.1.10 • PyPI Django: >= 2.2, < 2.2.3 → fixed in 2.2.3 • PyPI Django: >= 1.11, < 1.11.22 → fixed in 1.11.22

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.

Related

Alias · CVE (1)

  • 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. vulnerability

Weakness · CWE (1)

  • CWE-319 Cleartext Transmission of Sensitive Information weakness

References