SQL Injection Affecting python-django package, versions <2:4.0.6-1


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

Exploit Maturity
Proof of concept
EPSS
17.62% (97th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about SQL Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-PYTHONDJANGO-2940825
  • published5 Jul 2022
  • disclosed4 Jul 2022

Introduced: 4 Jul 2022

CVE-2022-34265  (opens in a new tab)
CWE-89  (opens in a new tab)

How to fix?

Upgrade Debian:unstable python-django to version 2:4.0.6-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-django package and not the python-django package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.

CVSS Scores

version 3.1