Vulnerability advisory

CVE-2022-28347

Published Updated OSV record ↗

Also known as BIT-django-2022-28347GHSA-w24h-v9qh-8gxjPYSEC-2022-191

Severity

Severity not reported.

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/django/django ↗
2a62cdcfec85938f40abb2e9e6a9ff497e02afe8 to before 5c3300027b30c1b498d99010f7d618316f6850455c3300027b30c1b498d99010f7d618316f685045
3591e1c1acbd7c13174275367c3fdf012cb0413b to before 08e6073f878264a0c091da0d3db456820252ef6c08e6073f878264a0c091da0d3db456820252ef6c
ef62a3a68c9d558486145a42c0d71ea9a76add9e to before 89807fbde8b7b17d00434bc4695535855e96fe7789807fbde8b7b17d00434bc4695535855e96fe77

Description

A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. This occurs by passing a crafted dictionary (with dictionary expansion) as the **options argument, and placing the injection payload in an option name.

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