PYSEC-2018-6
Vulnerability from pysec - Published: 2018-03-09 20:29 - Updated: 2021-06-10 06:52An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.
| Name | purl | django | pkg:pypi/django |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "django",
"purl": "pkg:pypi/django"
},
"ranges": [
{
"events": [
{
"introduced": "1.8"
},
{
"fixed": "1.8.19"
},
{
"introduced": "1.11"
},
{
"fixed": "1.11.11"
},
{
"introduced": "2.0"
},
{
"fixed": "2.0.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.11",
"1.11.1",
"1.11.10",
"1.11.2",
"1.11.3",
"1.11.4",
"1.11.5",
"1.11.6",
"1.11.7",
"1.11.8",
"1.11.9",
"1.8",
"1.8.1",
"1.8.10",
"1.8.11",
"1.8.12",
"1.8.13",
"1.8.14",
"1.8.15",
"1.8.16",
"1.8.17",
"1.8.18",
"1.8.2",
"1.8.3",
"1.8.4",
"1.8.5",
"1.8.6",
"1.8.7",
"1.8.8",
"1.8.9",
"2.0",
"2.0.1",
"2.0.2"
]
}
],
"aliases": [
"CVE-2018-7537",
"GHSA-2f9x-5v75-3qv4"
],
"details": "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. If django.utils.text.Truncator\u0027s chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.",
"id": "PYSEC-2018-6",
"modified": "2021-06-10T06:52:11.564894Z",
"published": "2018-03-09T20:29:00Z",
"references": [
{
"type": "ARTICLE",
"url": "https://www.djangoproject.com/weblog/2018/mar/06/security-releases/"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2018/03/msg00006.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/103357"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/3591-1/"
},
{
"type": "ADVISORY",
"url": "https://www.debian.org/security/2018/dsa-4161"
},
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2018:2927"
},
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2019:0265"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-2f9x-5v75-3qv4"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.