Is CVE-2022-28346 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-28346 being exploited in the wild.

How severe is CVE-2022-28346?

Low severity, with a CVSS score of 3.1, published 12 April 2022.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=2.2,fixed=2.2.28, ECOSYSTEM:introduced=4.0,fixed=4.0.4,introduced=3.2,fixed=3.2.13,introduced=2.2,fixed=2.2.28.

Is there a fix for CVE-2022-28346?

Yes. Django (PyPI): upgrade to 2.2.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2022-28346 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2022-28346?

Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2022-28346: PYSEC-2022-190 - An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra()

CVE-2022-28346 · Severity: low · CVSS 3.1 · Published 2022-04-12

Django is a popular Python web framework used to build web applications. The QuerySet.annotate(), aggregate(), and extra() methods were vulnerable to SQL injection attacks through crafted dictionary parameters, allowing attackers to execute arbitrary SQL commands and potentially access or modify sensitive database records.

Technologies: Django (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2022-28346 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2022-28346 being exploited in the wild.
How severe is CVE-2022-28346?: Low severity, with a CVSS score of 3.1, published 12 April 2022.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=2.2,fixed=2.2.28, ECOSYSTEM:introduced=4.0,fixed=4.0.4,introduced=3.2,fixed=3.2.13,introduced=2.2,fixed=2.2.28.
Is there a fix for CVE-2022-28346?: Yes. Django (PyPI): upgrade to 2.2.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2022-28346 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2022-28346?: Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Django (PyPI): upgrade to 2.2.28 or later
```
pip install "Django>=2.2.28"
```

Technical details

A SQL injection vulnerability (CWE-89) exists in Django's QuerySet.annotate(), aggregate(), and extra() methods due to insufficient input validation of column alias names passed via keyword arguments. An attacker can exploit this by crafting a malicious dictionary with specially-crafted keys that bypass alias validation, allowing arbitrary SQL injection when the dictionary is expanded as **kwargs. This is a network-accessible vulnerability requiring no authentication or user interaction. Successful exploitation allows an attacker to execute arbitrary SQL queries, potentially leading to data exfiltration, modification, or deletion. Patches are available in Django 2.2.28, 3.2.13, and 4.0.4 or later.

Affected products

Django Django 2.2 before 2.2.28, 3.2 before 3.2.13, 4.0 before 4.0.4

Identifiers

CVE-2022-28346
GHSA-2gwj-7jmv-h26r
PYSEC-2022-190

Timeline

2022-04-11: disclosed
2022-04-13: advisory
2022-04-11: patched: Patches available in Django 2.2.28, 3.2.13, and 4.0.4

References

https://github.com/django/django/commit/2044dac5c6968441be6f534c4139bcf48c5c7e48

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.