CVE-2019-12781
- State
- Published
- Severity
- Not scored
- Published
- Jul 1, 2019
- Updated
- Aug 4, 2024
- Reserved
- Jun 10, 2019
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.
Scores
The record has no CVSS score.
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
n/an/a |
|
References
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/forum/#%21topic/django-announce/Is4kLY9ZcZQ
- https://www.djangoproject.com/weblog/2019/jul/01/security-releases/
- [oss-security] 20190701 Django: CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPSmailing-list
- USN-4043-1vendor-advisory
- 109018vdb-entry
- https://security.netapp.com/advisory/ntap-20190705-0002/
- DSA-4476vendor-advisory
- 20190708 [SECURITY] [DSA 4476-1] python-django security updatemailing-list
- FEDORA-2019-d9aa58d863vendor-advisory
- openSUSE-SU-2019:1839vendor-advisory
- openSUSE-SU-2019:1872vendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.