CVE-2023-36053: High severity djangoproject Django vulnerability

Published Jun 27, 2023
·
Updated

EmailValidator and URLValidator were subject to potential regular expression denial of service attack via a very large number of domain name labels of emails and URLs.

Affected versions: Django main development branch, Django 4.2, Django 4.1, Django 3.2

Other sources

In Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3, EmailValidator and URLValidator are subject to a potential ReDoS (regular expression denial of service) attack via a very large number of domain name labels of emails and URLs.

In Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3, EmailValidator and URLValidator are subject to a potential ReDoS (regular expression denial of service) attack via a very large number of domain name labels of emails and URLs.

— GitHub

Affected Software

21 affected componentsFixes available
ubuntu/python-django<4.2.3, <4.1.10, <3.2.20
4.2.34.1.103.2.20
ubuntu/python-django<2:2.2.12-1ubuntu0.18
2:2.2.12-1ubuntu0.18
ubuntu/python-django<2:3.2.12-2ubuntu1.7
2:3.2.12-2ubuntu1.7
ubuntu/python-django<3:3.2.15-1ubuntu1.4
3:3.2.15-1ubuntu1.4
ubuntu/python-django<3:3.2.18-1ubuntu0.3
3:3.2.18-1ubuntu0.3
ubuntu/python-django<1:1.11.11-1ubuntu1.21+
1:1.11.11-1ubuntu1.21+
debian/python-django<=1:1.11.29-1~deb10u1
1: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.2a1<4.2.3
4.2.3
pip/Django>=4.0a1<4.1.10
4.1.10
pip/Django>=3.2a1<3.2.20
3.2.20
djangoproject Django>=3.2<3.2.20
djangoproject Django>=4.0<4.1.10
djangoproject Django>=4.2<4.2.3
Debian Debian Linux=10.0
Debian Debian Linux=11.0
Debian Debian Linux=12.0
Fedoraproject Fedora=37
Fedoraproject Fedora=38
redhat/python-django<4.2.3
4.2.3
redhat/python-django<4.1.10
4.1.10
redhat/python-django<3.2.20
3.2.20

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 4.2.3Fixed in 4.1.10Fixed in 3.2.20
  2. Upgrade

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

    Fixed in 2:2.2.12-1ubuntu0.18
  3. Upgrade

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

    Fixed in 2:3.2.12-2ubuntu1.7
  4. Upgrade

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

    Fixed in 3:3.2.15-1ubuntu1.4
  5. Upgrade

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

    Fixed in 3:3.2.18-1ubuntu0.3
  6. Upgrade

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

    Fixed in 1:1.11.11-1ubuntu1.21+
  7. Upgrade

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

    Fixed 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
  8. Upgrade

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

    Fixed in 4.2.3
  9. Upgrade

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

    Fixed in 4.1.10
  10. Upgrade

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

    Fixed in 3.2.20
  11. Upgrade

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

    Fixed in 4.2.3
  12. Upgrade

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

    Fixed in 4.1.10
  13. Upgrade

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

    Fixed in 3.2.20
  14. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 3.2.20
  15. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.1.10
  16. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.3

Event History

Jun 27, 2023
Data Sourced
via Red Hat·07:24 PM
DescriptionSeverityAffected Software
Jul 3, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·03:30 PM
Oct 17, 2023
Data Sourced
12:37 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID of this security issue?

The vulnerability ID is CVE-2023-36053.

2

What is the severity level of CVE-2023-36053?

The severity level of CVE-2023-36053 is high.

3

Which versions of Django are affected by CVE-2023-36053?

Django versions 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3 are affected by CVE-2023-36053.

4

What is the impact of CVE-2023-36053?

CVE-2023-36053 can lead to a potential ReDoS (regular expression denial of service) attack via a very large number of domain name labels of emails and URLs in Django applications.

5

How can I mitigate the vulnerability CVE-2023-36053?

To mitigate CVE-2023-36053, it is recommended to update Django to versions 3.2.20 or later, 4.1.10 or later, or 4.2.3 or later.

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