PYSEC-2019-85

Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing.

Not rated yet Withdrawn Mar 14, 2023 PyPI

Severity: Not rated yet; No source has published a CVSS score yet
Exploit chance (EPSS): —; No score published
Known exploited: No; Not in CISA's catalog
Weakness: —; Not classified
Fix: 2.2.8; Upgrade django to this version or later

Description

Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing. A Django model admin displaying inline related models, where the user has view-only permissions to a parent model but edit permissions to the inline model, would be presented with an editing UI, allowing POST requests, for updating the inline model. Directly editing the view-only parent model was not possible, but the parent model's save() method was called, triggering potential side effects, and causing pre and post-save signal handlers to be invoked. (To resolve this, the Django admin is adjusted to require edit permissions on the parent model in order for inline models to be editable.)

Affected versions

PyPI

Package	Vulnerable	Fixed in
django	`>= 2.1, < 2.1.15` `>= 2.2, < 2.2.8`	`2.1.15` `2.2.8`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

django PyPI → `2.2.8`

pip

pip install --upgrade "django>=2.2.8"

poetry

poetry add "django>=2.2.8"

uv

uv add "django>=2.2.8"

References

Timeline

Dec 2, 2019 Published
Mar 14, 2023 Last updated by the source
Mar 14, 2023 Withdrawn

Advisory	Severity	Why it's related
GHSA-q238-5cxm-5c9h Django GeoDjango vulnerable to denial of service through deeply nested geometry collections	Medium	Also affects django
GHSA-wvqv-fj8w-qmhm Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing	High	Also affects django
GHSA-8qcx-xf44-272x Django: DomainNameValidator permits newline characters that may enable HTTP header injection	Medium	Also affects django
GHSA-crhf-3pfg-w68w Django: GDALRaster may over-read heap memory when constructed from bytes	Medium	Also affects django
GHSA-3h9f-r86x-qvjx Django: cache middleware may expose private responses when unrelated request cookies are present	Medium	Also affects django
GHSA-8cjm-8mp7-r2xf Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling	Medium	Also affects django
GHSA-mm6v-q8q9-pgcf Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake	Low	Also affects django
GHSA-h7pc-vwp9-298g Django: signed cookies are vulnerable to salt namespace collisions	Medium	Also affects django

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor