Advisory

GHSA-6c7v-2f49-8h26

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

Summary

Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2019-07-03 20:37 UTC
Modified
2024-09-18 16:26 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 2.1, fixed 2.1.10 (ecosystem)

Fixed versions

2.1.10

Fix

  • Fixed version 2.1.10
    pip install --upgrade django==2.1.10

django

PyPI · All systems

Affected

  • introduced 2.2, fixed 2.2.3 (ecosystem)

Fixed versions

2.2.3

Fix

  • Fixed version 2.2.3
    pip install --upgrade django==2.2.3

django

PyPI · All systems

Affected

  • introduced 1.11, fixed 1.11.22 (ecosystem)

Fixed versions

1.11.22

Fix

  • Fixed version 1.11.22
    pip install --upgrade django==1.11.22

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences