CVE-2022-41323: High severity djangoproject Django vulnerability

Published Oct 4, 2022
·
Updated

A denial of service flaw was discovered in Django. This issue occurs when incorrectly handling certain internationalized URLs. A malicious attacker could use this issue to cause a crash, resulting in a denial of service.

Other sources

In Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service attack via the locale parameter, which is treated as a regular expression.

Affected Software

9 affected componentsFixes available
redhat/python-django<0:3.2.18-1.el8
0:3.2.18-1.el8
redhat/python-django<0:3.2.16-1.0.1.el8
0:3.2.16-1.0.1.el8
debian/python-django
1:1.11.29-1~deb10u11:1.11.29-1+deb10u102:2.2.28-1~deb11u23:3.2.19-1+deb12u13:3.2.21-13:4.2.8-1
pip/django>=4.1<4.1.2
4.1.2
pip/django>=4.0<4.0.8
4.0.8
pip/django>=3.2<3.2.16
3.2.16
djangoproject Django>=3.2<3.2.16
djangoproject Django>=4.0<4.0.8
djangoproject Django>=4.1<4.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/python-django to a version that resolves this vulnerability.

    Fixed in 0:3.2.18-1.el8
  2. Upgrade

    Upgrade redhat/python-django to a version that resolves this vulnerability.

    Fixed in 0:3.2.16-1.0.1.el8
  3. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 1:1.11.29-1~deb10u1Fixed in 1:1.11.29-1+deb10u10Fixed in 2:2.2.28-1~deb11u2Fixed in 3:3.2.19-1+deb12u1Fixed in 3:3.2.21-1Fixed in 3:4.2.8-1
  4. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 4.1.2
  5. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 4.0.8
  6. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 3.2.16
  7. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 3.2.16
  8. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.0.8
  9. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.1.2

Event History

Oct 4, 2022
CVE Published
12:00 AM
Oct 16, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·12:00 PM
Oct 19, 2022
Data Sourced
via Red Hat·12:08 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2022-41323?

The severity of CVE-2022-41323 is high.

2

How do I fix CVE-2022-41323?

To fix CVE-2022-41323, update Django to version 4.1.2, 4.0.8, or 3.2.16 depending on your current version.

3

What is the impact of CVE-2022-41323?

CVE-2022-41323 can be exploited by a malicious attacker to cause a crash, resulting in a denial of service.

4

Where can I find more information about CVE-2022-41323?

You can find more information about CVE-2022-41323 on the NIST NVD website, Django's GitHub repository, and the Django website.

5

What is the CWE ID of CVE-2022-41323?

The CWE ID of CVE-2022-41323 is 400.

Company

Resources

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