VDB

CVE-2019-12781

CVE-2019-12781 PUBLISHED CVSS 5.300000190734863 MEDIUM

Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS

Reported by mitre · Published July 1, 2019

Django is fixed in 2.2.3, 2.1.10 and 1.11.22 (PyPI)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
DjangoPyPI2.2.3, 2.1.10, 1.11.22
py3-djangoAlpine1.11.22-r0
py-djangoAlpine1.11.22-r0
python-djangoUbuntu:16.04:LTS1.8.7-1ubuntu5.9
djangodjangoproject2.2.3, 2.1.10, 1.11.22

Risk scores

CVSS 3.0
5.300000190734863
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

VendorProductVersions
n/an/an/a
alpinepy3-django0
alpinepy-django0
n/an/a*
archpython-django0
PyPIDjango2.1, 2.2, 1.11

Timeline

  • Jul 1, 2019 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Sep 18, 2024 CVE Updated
  • Mar 6, 2026 Distribution Patch (2 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (7 in total, the first dated here)
  • Sep 15, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2019-12781
vulnetix vdb fixes CVE-2019-12781

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2019-12781/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›