Django denial-of-service possibility in urlize and urlizetrunc template filters
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
1.8.19An 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.
From the CVE record · mitre
Django’s django.utils.html.urlize() is extremely slow on certain inputs because of catastrophic regular-expression backtracking. The urlize and urlizetrunc template filters use this function, so an attacker who can supply input to them may cause excessive processing. The input does not specify whether authentication or user interaction is required.
Teams running the PyPI django package should check versions 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19, including affected prereleases.