CVE-2021-44420: High severity django vulnerability

Published Dec 1, 2021
·
Updated

HTTP requests for URLs with trailing newlines could bypass an upstream access control based on URL paths.

Other sources

In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths.

Affected Software

18 affected componentsFixes available
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 Debian Linux=10.0
Debian Debian Linux=11.0
Canonical Ubuntu Linux=20.04
Canonical Ubuntu Linux=21.04
Canonical Ubuntu Linux=21.10
Fedoraproject Fedora=35

Event History

Dec 7, 2021
CVE Published
08:00 AM
CVE Published
via MITRE·10:55 PM
Data Sourced
via MITRE·10:55 PM
Description
Dec 8, 2021
Data Sourced
via NVD·12:15 AM
RemedyDescriptionSeverityAffected Software
Dec 9, 2021
Advisory Published
via GitHub·07:09 PM

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2021-44420?

The severity of CVE-2021-44420 is medium, with a severity value of 5.3.

2

How can HTTP requests with trailing newlines bypass access control in Django versions affected by CVE-2021-44420?

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.

3

Which versions of Django are affected by CVE-2021-44420?

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.

4

How do I fix CVE-2021-44420 in Django?

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.

5

Where can I find more information about CVE-2021-44420?

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203