DemoBook a demo

Vulnerability advisory

CVE-2019-12781

Published Updated OSV record ↗

Also known as GHSA-6c7v-2f49-8h26PYSEC-2019-10

Severity
  • CVSS 3.xCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/django/django ↗
c669cf279ae7b3e02a61db4fb077030a4db80e4f to before 480380c9935a2e920a41828b3a07bee66a686a67480380c9935a2e920a41828b3a07bee66a686a67
df591468251ed489a3e147d7c359f387f4effe66 to before 90a1cfd60002c465d9c47ad9ebc0a79ad0bc6cf990a1cfd60002c465d9c47ad9ebc0a79ad0bc6cf9
2a62cdcfec85938f40abb2e9e6a9ff497e02afe8 to before 89e9a4aeb62ff63ae2d387b1142d6ddaa842d66d89e9a4aeb62ff63ae2d387b1142d6ddaa842d66d

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.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools

Having trouble? Check our documentation.