CVE-2019-19118
First published: Mon Dec 02 2019(Updated: )
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.)
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Djangoproject Django | >=2.1<2.1.15 | |
| Djangoproject Django | >=2.2<2.2.8 | |
| Fedoraproject Fedora | =31 | |
| pip/Django | >=2.2<2.2.8 | 2.2.8 |
| pip/Django | >=2.1<2.1.15 | 2.1.15 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.openwall.com/lists/oss-security/2019/12/02/1
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/forum/#!topic/django-announce/GjGqDvtNmWQ
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6R4HD22PVEVQ45H2JA2NXH443AYJOPL5/
- https://security.gentoo.org/glsa/202004-17
- https://security.netapp.com/advisory/ntap-20191217-0003/
- https://www.djangoproject.com/weblog/2019/dec/02/security-releases/
- https://groups.google.com/forum/#%21topic/django-announce/GjGqDvtNmWQ
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6R4HD22PVEVQ45H2JA2NXH443AYJOPL5/
- https://nvd.nist.gov/vuln/detail/CVE-2019-19118
- https://github.com/django/django/commit/103ebe2b5ff1b2614b85a52c239f471904d26244
- https://github.com/django/django/commit/36f580a17f0b3cb087deadf3b65eea024f479c21
- https://docs.djangoproject.com/en/dev/releases/security
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6R4HD22PVEVQ45H2JA2NXH443AYJOPL5
- https://security.netapp.com/advisory/ntap-20191217-0003
- https://www.djangoproject.com/weblog/2019/dec/02/security-releases
- https://github.com/advisories/GHSA-hvmf-r92r-27hr (Advisory)
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2019-15.yaml
Frequently Asked Questions
What is the vulnerability ID of this issue?
The vulnerability ID of this issue is CVE-2019-19118.
What is the severity level of CVE-2019-19118?
CVE-2019-19118 has a severity level of medium.
Which versions of Django are affected by CVE-2019-19118?
Django versions 2.1 before 2.1.15 and 2.2 before 2.2.8 are affected by CVE-2019-19118.
What is the impact of CVE-2019-19118?
CVE-2019-19118 allows unintended model editing in Django model admin.
How can I fix CVE-2019-19118?
To fix CVE-2019-19118, upgrade Django to version 2.1.15 or 2.2.8 or newer.
- collector/nvd-index
- agent/type
- agent/severity
- agent/weakness
- agent/remedy
- agent/description
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/first-publish-date
- agent/event
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-hvmf-r92r-27hr
- alias/CVE-2019-19118
- agent/references
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- collector/github-advisory
- vendor/djangoproject
- canonical/djangoproject django
- version/djangoproject django/2.1
- version/djangoproject django/2.2
- vendor/fedoraproject
- canonical/fedoraproject fedora
- version/fedoraproject fedora/31
- package-manager/pip