Homepage
About Snyk

SQL Injection Affecting python-django package, versions <2:2.2.28-1~deb11u1

0.0
critical

Snyk CVSS

    Attack Complexity Low
    Confidentiality High
    Integrity High
    Availability High

    Threat Intelligence

    Exploit Maturity Proof of concept
    EPSS 11.74% (96th percentile)
Expand this section
NVD
9.8 critical
Expand this section
Red Hat
9.8 critical

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 ID SNYK-DEBIAN11-PYTHONDJANGO-2940827
  • published 5 Jul 2022
  • disclosed 4 Jul 2022
Report a new vulnerability Found a mistake?

Introduced: 4 Jul 2022

CVE-2022-34265 Open this link in a new tab
CWE-89 Open this link in a new tab

How to fix?

Upgrade Debian:11 python-django to version 2:2.2.28-1~deb11u1 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:11 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.

References