First published: Wed Dec 01 2021(Updated: )
HTTP requests for URLs with trailing newlines could bypass an upstream access control based on URL paths.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/python-django | <0:3.2.13-1.el8 | 0:3.2.13-1.el8 |
redhat/python-django | <0:3.2.16-1.0.1.el8 | 0:3.2.16-1.0.1.el8 |
redhat/django | <3.2.10 | 3.2.10 |
redhat/django | <3.1.14 | 3.1.14 |
redhat/django | <2.2.25 | 2.2.25 |
pip/Django | >=3.2a1<3.2.10 | 3.2.10 |
pip/Django | >=3.0a1<3.1.14 | 3.1.14 |
pip/Django | >=2.2a1<2.2.25 | 2.2.25 |
djangoproject Django | >=2.2<2.2.25 | |
djangoproject Django | >=3.1<3.1.14 | |
djangoproject Django | >=3.2<3.2.10 | |
redhat satellite | =6.0 | |
Debian | =10.0 | |
Debian | =11.0 | |
Ubuntu | =20.04 | |
Ubuntu | =21.04 | |
Ubuntu | =21.10 | |
Fedora | =35 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2021-44420 is medium, with a severity value of 5.3.
HTTP requests with trailing newlines can bypass access control in Django versions affected by CVE-2021-44420 by exploiting a vulnerability in how URLs with trailing newlines are handled.
Django versions 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10 are affected by CVE-2021-44420.
To fix CVE-2021-44420 in Django, you should update to version 2.2.25, 3.1.14, or 3.2.10, depending on the version you are currently using.
You can find more information about CVE-2021-44420 on the CVE website, the NIST NVD website, the Django security releases blog post, the Red Hat Bugzilla page, and the Red Hat access portal.