ALPINE-CVE-2019-12781
Record from OSV · Published July 1, 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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| py-django | Alpine:v3.7 | 1.11.22-r0 |
| py3-django | Alpine:v3.11 | 1.11.22-r0 |
| py-django | Alpine:v3.8 | 1.11.22-r0 |
| py-django | Alpine:v3.9 | 1.11.22-r0 |
| py3-django | Alpine:v3.12 | 1.11.22-r0 |
| py-django | Alpine:v3.10 | 1.11.22-r0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Alpine:v3.7 | py-django | 0, 1.11-r0, 1.8.14-r0 |
| Alpine:v3.11 | py3-django | 1.5.8-r0, 1.6.6-r0, 1.8.8-r0 |
| Alpine:v3.8 | py-django | 1.8.6-r0, 1.7-r0, 1.8.14-r0 |
| Alpine:v3.9 | py-django | 1.7-r0, 0, 1.10.7-r0 |
| Alpine:v3.12 | py3-django | 1.8.15-r0, 1.4.1-r0, 1.2.5-r1 |
| Alpine:v3.10 | py-django | 1.11.10-r0, 1.10.5-r0, 1.11-r1 |
Timeline
- Jul 1, 2019 CVE Published
- Nov 19, 2025 CVE Updated
- Aug 8, 2026 Distribution Patch
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln ALPINE-CVE-2019-12781
vulnetix vdb fixes ALPINE-CVE-2019-12781
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/ALPINE-CVE-2019-12781/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart