CVE-2018-7536
- State
- Published
- Severity
- Not scored
- Published
- Mar 9, 2018
- Updated
- Aug 5, 2024
- Reserved
- Feb 26, 2018
Description
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.
Scores
The record has no CVSS score.
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
n/an/a |
|
References
- USN-3591-1vendor-advisory
- RHSA-2019:0051vendor-advisory
- [debian-lts-announce] 20180308 [SECURITY] [DLA 1303-1] python-django security updatemailing-list
- 103361vdb-entry
- https://www.djangoproject.com/weblog/2018/mar/06/security-releases/
- RHSA-2019:0082vendor-advisory
- RHSA-2018:2927vendor-advisory
- RHSA-2019:0265vendor-advisory
- DSA-4161vendor-advisory
- https://github.com/django/django/commit/1ca63a66ef3163149ad822701273e8a1844192c2
- https://github.com/django/django/commit/abf89d729f210c692a50e0ad3f75fb6bec6fae16
- https://github.com/django/django/commit/e157315da3ae7005fa0683ffc9751dbeca7306c8
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.