CVE-2019-12781

Aliases:GHSA-6c7v-2f49-8h26PYSEC-2019-10
Advisory lineage Upstream: 0 Downstream: 19
Modified
Published: 01 Jul 2019, 13:56
Last modified:04 Aug 2024, 23:32

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.3 MEDIUM
v3.0 (nvd)
EPSS Score
4.22% LOW
4% probability +0.32%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

01 Jul 2019, 13:56
Published
Vulnerability first disclosed
04 Aug 2024, 23:32
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v4.0•MEDIUM•Score: 6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
  • v3.0•MEDIUM•Score: 5.3CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
  • v2.0•MEDIUM•Score: 5AV:N/AC:L/Au:N/C:P/I:N/A:N

EPSS Trends

Current EPSS score: 4.22%• Percentile: 89%

Techniques & Countermeasures

  • CWE-319•Cleartext Transmission of Sensitive Information

    The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

Affected Systems

  • canonical•ubuntu_linux

    16.04 | 18.04 | 18.10 | 19.04

  • debian•debian_linux

    9.0

  • djangoproject•django

    ≥ 1.11, < 1.11.22 | ≥ 2.1, < 2.1.10 | ≥ 2.2, < 2.2.3

  • PyPI•django

    ≥ 2.1, < 2.1.10 | ≥ 2.2, < 2.2.3 | ≥ 1.11, < 1.11.22

References (23)