Potential SQL injection in FilteredRelation column aliases on PostgreSQL
djangoproject Django
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
djangoproject Django
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
4.2.27An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27. `FilteredRelation` is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the `**kwargs` passed to `QuerySet.annotate()` or `QuerySet.alias()` on PostgreSQL. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Stackered for reporting this issue.
From the CVE record · DSF
On PostgreSQL, Django’s FilteredRelation is vulnerable to SQL injection in column aliases when a crafted dictionary is expanded as keyword arguments to QuerySet.annotate() or QuerySet.alias(). The input does not specify whether exploitation requires network access, authentication, or user interaction.
Teams running the PyPI django package should check 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27; earlier unsupported series were not evaluated and may also be affected.