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.
Published: 2019-07-01
Score: 5.3 Medium
EPSS: 3.9% Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-4476-1 python-django security update
Github GHSA Github GHSA GHSA-6c7v-2f49-8h26 Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS
Ubuntu USN Ubuntu USN USN-4043-1 Django vulnerabilities
History

No history.

Subscriptions

Canonical Ubuntu Linux
Debian Debian Linux
Djangoproject Django
Redhat Openstack Satellite Satellite Capsule
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-04T23:32:54.914Z

Reserved: 2019-06-10T00:00:00.000Z

Link: CVE-2019-12781

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-07-01T14:15:10.847

Modified: 2024-11-21T04:23:33.900

Link: CVE-2019-12781

cve-icon Redhat

Severity : Moderate

Publid Date: 2019-07-01T00:00:00Z

Links: CVE-2019-12781 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses