VYPR
High severityNVD Advisory· Published Aug 2, 2019· Updated Aug 5, 2024

CVE-2019-14233

CVE-2019-14233

Description

An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to the behaviour of the underlying HTMLParser, django.utils.html.strip_tags would be extremely slow to evaluate certain inputs containing large sequences of nested incomplete HTML entities.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Django's strip_tags() can be abused to cause a denial-of-service via crafted input with nested incomplete HTML entities, due to inefficient HTMLParser behavior.

Vulnerability

Overview

CVE-2019-14233 is a denial-of-service (DoS) vulnerability in Django's django.utils.html.strip_tags function. The root cause lies in the behavior of the underlying HTMLParser when evaluating certain inputs containing large sequences of nested incomplete HTML entities. This leads to extreme slowness, allowing an attacker to exhaust server resources [1][2].

Attack

Vector

An attacker can exploit this vulnerability by providing specially crafted input to any application that uses the strip_tags function or related template filters (e.g., striptags). No authentication is required if the input is user-controlled, and the attack can be performed remotely over HTTP. The crafted input triggers catastrophic backtracking or excessive processing in the HTML parser, resulting in a denial-of-service condition [3][4].

Impact

Successful exploitation allows an attacker to cause the Django application to consume excessive CPU time, potentially leading to a full denial-of-service for legitimate users. The vulnerability does not lead to data disclosure or privilege escalation, but it can disrupt application availability [1][4].

Mitigation

Django released patched versions 1.11.23, 2.1.11, and 2.2.4 on August 1, 2019, which address this issue by improving the handling of HTML entities within strip_tags. All users running affected versions are strongly advised to upgrade immediately. No workaround is available other than applying the patch [1][4].

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
DjangoPyPI
>= 1.11a1, < 1.11.231.11.23
DjangoPyPI
>= 2.1a1, < 2.1.112.1.11
DjangoPyPI
>= 2.2a1, < 2.2.42.2.4

Affected products

10

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

18

News mentions

0

No linked articles in our index yet.