CVE-2018-7536
published 2018-03-09CVE-2018-7536: An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to…
PriorityP431medium5.3CVSS 3.0
AVNACLPRNUINSUCNINAL
EPSS
4.60%
90.6th percentile
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | python-django | < python-django 1:1.11.11-1 (bookworm) | python-django 1:1.11.11-1 (bookworm) |
| djangoproject | django | >= 1.11 < 1.11.11 | 1.11.11 |
| djangoproject | django | >= 1.11a1 < 1.11.11 | 1.11.11 |
| djangoproject | django | >= 1.8 < 1.8.19 | 1.8.19 |
| djangoproject | django | >= 1.8a1 < 1.8.19 | 1.8.19 |
| djangoproject | django | >= 2.0 < 2.0.3 | 2.0.3 |
| djangoproject | django | >= 2.0a1 < 2.0.3 | 2.0.3 |
| redhat | openstack | — | — |
| redhat | openstack | — | — |
CVSS provenance
nvdv3.05.3MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv5.3MEDIUM
vendor_debian5.3MEDIUM
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Django denial-of-service possibility in urlize and urlizetrunc template filters
osv·2019-01-04
CVE-2018-7536 [MEDIUM] Django denial-of-service possibility in urlize and urlizetrunc template filters
Django denial-of-service possibility in urlize and urlizetrunc template filters
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The `django.utils.html.urlize()` function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The `urlize()` function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.
GHSA
Django denial-of-service possibility in urlize and urlizetrunc template filters
ghsa·2019-01-04
CVE-2018-7536 [MEDIUM] CWE-185 Django denial-of-service possibility in urlize and urlizetrunc template filters
Django denial-of-service possibility in urlize and urlizetrunc template filters
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The `django.utils.html.urlize()` function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The `urlize()` function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.
OSV
CVE-2018-7536: An issue was discovered in Django 2
osv·2018-03-09·CVSS 5.3
CVE-2018-7536 [MEDIUM] CVE-2018-7536: An issue was discovered in Django 2
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.
Ubuntu
Django vulnerabilities
vendor_ubuntu·2018-03-06
CVE-2018-7536 Django vulnerabilities
Title: Django vulnerabilities
Summary: Several security issues were fixed in Django.
James Davis discovered that Django incorrectly handled certain template
filters. A remote attacker could possibly use this issue to cause Django
to consume resources, resulting in a denial of service.
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
django: Catastrophic backtracking in regular expressions via 'urlize' and 'urlizetrunc'
vendor_redhat·2018-03-06·CVSS 5.3
CVE-2018-7536 [MEDIUM] CWE-20 django: Catastrophic backtracking in regular expressions via 'urlize' and 'urlizetrunc'
django: Catastrophic backtracking in regular expressions via 'urlize' and 'urlizetrunc'
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.
Statement: This issue affects the versions of django as shipped with Red Hat Subscription Asset Manager. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Cl
Debian
CVE-2018-7536: python-django - An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8...
vendor_debian·2018·CVSS 5.3
CVE-2018-7536 [MEDIUM] CVE-2018-7536: python-django - An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8...
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.
Scope: local
bookworm: resolved (fixed in 1:1.11.11-1)
bullseye: resolved (fixed in 1:1.11.11-1)
forky: resolved (fixed in 1:1.11.11-1)
sid: resolved (fixed in 1:1.11.11-1)
trixie: resolved (fixed in 1:1.11.11-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-7536 CVE-2018-7537 python-django16: various flaws [epel-7]
bugzilla·2018-03-06·CVSS 5.3
CVE-2018-7536 [MEDIUM] CVE-2018-7536 CVE-2018-7537 python-django16: various flaws [epel-7]
CVE-2018-7536 CVE-2018-7537 python-django16: various flaws [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update'
Bugzilla
CVE-2018-7536 CVE-2018-7537 python-django: various flaws [fedora-all]
bugzilla·2018-03-06·CVSS 5.3
CVE-2018-7536 [MEDIUM] CVE-2018-7536 CVE-2018-7537 python-django: various flaws [fedora-all]
CVE-2018-7536 CVE-2018-7537 python-django: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedo
Bugzilla
CVE-2018-7536 CVE-2018-7537 python-django: various flaws [epel-7]
bugzilla·2018-03-06·CVSS 5.3
CVE-2018-7536 [MEDIUM] CVE-2018-7536 CVE-2018-7537 python-django: various flaws [epel-7]
CVE-2018-7536 CVE-2018-7537 python-django: various flaws [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' r
Bugzilla
CVE-2018-7536 django: Catastrophic backtracking in regular expressions via 'urlize' and 'urlizetrunc'
bugzilla·2018-02-27·CVSS 5.3
CVE-2018-7536 [MEDIUM] CVE-2018-7536 django: Catastrophic backtracking in regular expressions via 'urlize' and 'urlizetrunc'
CVE-2018-7536 django: Catastrophic backtracking in regular expressions via 'urlize' and 'urlizetrunc'
CVE-2018-7536: Denial-of-service possibility in ``urlize`` and
``urlizetrunc`` template filters
The ``django.utils.html.urlize()`` function was extremely slow to evaluate
certain inputs due to catastrophic backtracking vulnerabilities in two
regular expressions (one regular expression for Django 1.8). The
``urlize()``
function is used to implement the ``urlize`` and ``urlizetrunc`` template
filters, which were thus vulnerable.
The problematic regular expressions are replaced with parsing logic that
behaves similarly.
Discussion:
Acknowledgments:
Name: the Django project
---
External References:
https://www.djangoproject.com/weblog/2018/mar/06/security-releases/
---
Created pytho
http://www.securityfocus.com/bid/103361https://access.redhat.com/errata/RHSA-2018:2927https://access.redhat.com/errata/RHSA-2019:0051https://access.redhat.com/errata/RHSA-2019:0082https://access.redhat.com/errata/RHSA-2019:0265https://github.com/django/django/commit/1ca63a66ef3163149ad822701273e8a1844192c2https://github.com/django/django/commit/abf89d729f210c692a50e0ad3f75fb6bec6fae16https://github.com/django/django/commit/e157315da3ae7005fa0683ffc9751dbeca7306c8https://lists.debian.org/debian-lts-announce/2018/03/msg00006.htmlhttps://usn.ubuntu.com/3591-1/https://www.debian.org/security/2018/dsa-4161https://www.djangoproject.com/weblog/2018/mar/06/security-releases/http://www.securityfocus.com/bid/103361https://access.redhat.com/errata/RHSA-2018:2927https://access.redhat.com/errata/RHSA-2019:0051https://access.redhat.com/errata/RHSA-2019:0082https://access.redhat.com/errata/RHSA-2019:0265https://github.com/django/django/commit/1ca63a66ef3163149ad822701273e8a1844192c2https://github.com/django/django/commit/abf89d729f210c692a50e0ad3f75fb6bec6fae16https://github.com/django/django/commit/e157315da3ae7005fa0683ffc9751dbeca7306c8https://lists.debian.org/debian-lts-announce/2018/03/msg00006.htmlhttps://usn.ubuntu.com/3591-1/https://www.debian.org/security/2018/dsa-4161https://www.djangoproject.com/weblog/2018/mar/06/security-releases/
2018-03-09
Published