CVE-2019-12781

high
Published 2019-07-03 ยท Modified 2023-11-08
CVSS v3
โ€”
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
8.0

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.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

suse SUSE Affected 1 release
VersionStatusFixed in
โ€” Affected โ€”
arch Arch Fixed 1 release
VersionStatusFixed in
โ€” Fixed 2.2.3-1
debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 1:1.11.22-1
sid Fixed 1:1.11.22-1
forky Fixed 1:1.11.22-1
bullseye Fixed 1:1.11.22-1
bookworm Fixed 1:1.11.22-1

Package impact

EcosystemPackageVulnerableFixed
python PyPIdjango>=2.1,<2.1.102.1.10
python PyPIdjango>=2.2,<2.2.32.2.3
python PyPIdjango>=1.11,<1.11.221.11.22

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.