LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34265: An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-34265 is a Django SQL injection issue. It affects Django 3.2 before 3.2.14 and 4.0 before 4.0.6 when applications pass untrusted values into specific date/time database function parameters. Applications using a fixed safe list for those choices are described as unaffected.

Executive priority

Treat this as a targeted but real application risk. Patch affected Django versions and verify whether product features expose user-controlled date/time function choices. Escalate priority if affected code is reachable from public or partner-facing applications.

Technical view

Django Trunc() and Extract() database functions may be vulnerable when untrusted input controls kind or lookup_name. The issue is fixed in Django 3.2.14 and 4.0.6. The source bundle provides no CVSS score and no KEV listing, so exploitation status is not established here.

Likely exposure

Exposure is most likely in Django applications on the affected versions that let users influence date/time grouping, filtering, reporting, or annotation logic using Trunc() or Extract(). Applications constraining those values to known safe choices are stated as unaffected.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The practical risk depends on whether application code passes attacker-controlled values into the affected function parameters.

Researcher notes

The key evidence gap is exploitability in a specific application. Focus review on data flow into Trunc(kind=...) and Extract(lookup_name=...). Do not assume all Django applications are exploitable; the CVE explicitly excludes safe-listed choices.

Mitigation direction

  • Upgrade Django 3.2 deployments to 3.2.14 or later.
  • Upgrade Django 4.0 deployments to 4.0.6 or later.
  • Restrict Trunc kind choices to a known safe list.
  • Restrict Extract lookup_name choices to a known safe list.
  • Check Debian, Fedora, NetApp, and vendor guidance for packaged fixes.

Validation and detection

  • Inventory deployed Django versions across applications and containers.
  • Review code for Trunc() and Extract() usage.
  • Confirm kind and lookup_name cannot come directly from untrusted input.
  • Verify dependency locks or packages include fixed Django releases.
  • Prioritize review of reporting, filtering, analytics, and date grouping features.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-34265 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.