What’s Vulnerable › Vulnerabilities

CVE-2019-12781

• Severity: medium (CVSS 5.3 v3.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 1.7% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2019-07-01 · updated 2026-06-17
• Weakness: CWE-319

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.

Affected products

• Canonical Ubuntu Linux: 16.04, 18.04, 18.10, 19.04
• Debian Linux: 9.0
• Django: from 1.11 before 1.11.22; from 2.1 before 2.1.10; from 2.2 before 2.2.3 — fixed in 1.11.22, 2.1.10, 2.2.3

How to fix

Upgrade to a fixed version: Django 1.11.22, 2.1.10, 2.2.3. Check the vendor advisory for mitigations.

References

• http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html
• http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html
• http://www.openwall.com/lists/oss-security/2019/07/01/3
• http://www.securityfocus.com/bid/109018
• https://docs.djangoproject.com/en/dev/releases/security/
• https://groups.google.com/forum/#%21topic/django-announce/Is4kLY9ZcZQ
• https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL/
• https://seclists.org/bugtraq/2019/Jul/10
• https://security.netapp.com/advisory/ntap-20190705-0002/
• https://usn.ubuntu.com/4043-1/
• https://www.debian.org/security/2019/dsa-4476
• https://www.djangoproject.com/weblog/2019/jul/01/security-releases/

Get alerted when CVE-2019-12781 or the next vulnerability affects your stack