First published: Mon Feb 11 2019(Updated: )
Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied value to the `django.utils.numberformat.format()` function.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | >=1.11.0<1.11.19 | |
Djangoproject Django | >=2.0.0<2.0.11 | |
Djangoproject Django | >=2.1.0<2.1.6 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =18.10 | |
Fedoraproject Fedora | =28 | |
Fedoraproject Fedora | =29 | |
pip/Django | >=2.1<2.1.6 | 2.1.6 |
pip/Django | >=2.0<2.0.11 | 2.0.11 |
pip/Django | >=1.11<1.11.19 | 1.11.19 |
debian/python-django | 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:4.2.16-1 3:4.2.17-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-6975 is high with a CVSS score of 7.5.
CVE-2019-6975 affects Django versions 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6.
CVE-2019-6975 allows uncontrolled memory consumption in Django via a malicious attacker-supplied value to the `django.utils.numberformat.format()` function.
To fix CVE-2019-6975 on Django, you should upgrade to version 1.11.19, 2.0.11, or 2.1.6, depending on the affected version.
You can find more information about CVE-2019-6975 on the NIST website (https://nvd.nist.gov/vuln/detail/CVE-2019-6975), the Django security releases (https://docs.djangoproject.com/en/dev/releases/security/), and the Django-announce Google Group (https://groups.google.com/forum/#!topic/django-announce/WTwEAprR0IQ).