CVE-2019-12781
Published: 1 July 2019
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.
Priority
Status
Package | Release | Status |
---|---|---|
python-django Launchpad, Ubuntu, Debian |
bionic |
Released
(1:1.11.11-1ubuntu1.4)
|
cosmic |
Released
(1:1.11.15-1ubuntu1.3)
|
|
disco |
Released
(1:1.11.20-1ubuntu0.1)
|
|
focal |
Not vulnerable
(1:1.11.22-1)
|
|
jammy |
Not vulnerable
(1:1.11.22-1)
|
|
kinetic |
Not vulnerable
(1:1.11.22-1)
|
|
lunar |
Not vulnerable
(1:1.11.22-1)
|
|
mantic |
Not vulnerable
(1:1.11.22-1)
|
|
trusty |
Needed
|
|
upstream |
Needs triage
|
|
xenial |
Released
(1.8.7-1ubuntu5.9)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 5.3 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | Low |
Integrity impact | None |
Availability impact | None |
Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |