NVD / CVE Program· CNA mitre

CVE-2019-14233: 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.

HighCVSS 7.5 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 88.2% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: py-django (Alpine:v3.10) 1.11.23-r0; py3-django (Alpine:v3.11) 1.11.23-r0; python-django (Debian:10) 1:1.11.23-1~deb10u1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to py-django (Alpine:v3.10) 1.11.23-r0; py3-django (Alpine:v3.11) 1.11.23-r0; python-django (Debian:10) 1:1.11.23-1~deb10u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Aug 2, 2019
Updated: Jun 16, 2026
EPSS: 3.1% · 88th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 3.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
djangoproject	django	cpe:2.3:a:djangoproject:django
opensuse	leap	cpe:2.3:o:opensuse:leap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

djangoproject django1.11 and later · before 1.11.23
djangoproject django2.1 and later · before 2.1.11
djangoproject django2.2 and later · before 2.2.4
opensuse leap15.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.10	py-django	before 1.11.23-r0	1.11.23-r0
Alpine:v3.11	py3-django	before 1.11.23-r0	1.11.23-r0
Debian:10	python-django	before 1:1.11.23-1~deb10u1	1:1.11.23-1~deb10u1
Debian:12	python-django	before 2:2.2.4-1	2:2.2.4-1
Debian:8	python-django	before 1.7.11-1+deb8u7	1.7.11-1+deb8u7
Debian:9	python-django	before 1:1.10.7-2+deb9u6	1:1.10.7-2+deb9u6
openSUSE:Leap 15.1	python-Django	before 2.2.4-lp151.2.3.1	2.2.4-lp151.2.3.1
PyPI	django	from 1.11 · before 1.11.23	1.11.23
PyPI	django	from 1.11a1 · before 1.11.23	1.11.23
PyPI	django	from 2.1 · before 2.1.11	2.1.11
PyPI	django	from 2.1a1 · before 2.1.11	2.1.11
PyPI	django	from 2.2 · before 2.2.4	2.2.4
PyPI	django	from 2.2a1 · before 2.2.4	2.2.4
Red Hat:openstack:13::el7	python-django	before 0:1.11.27-1.el7ost	0:1.11.27-1.el7ost
Red Hat:openstack:13::el7	python-django-bash-completion	before 0:1.11.27-1.el7ost	0:1.11.27-1.el7ost
Red Hat:openstack:13::el7	python2-django	before 0:1.11.27-1.el7ost	0:1.11.27-1.el7ost
Red Hat:openstack:15::el8	python-django	before 0:2.1.11-1.el8ost	0:2.1.11-1.el8ost
Red Hat:openstack:15::el8	python-django-bash-completion	before 0:2.1.11-1.el8ost	0:2.1.11-1.el8ost
Red Hat:openstack:15::el8	python3-django	before 0:2.1.11-1.el8ost	0:2.1.11-1.el8ost
SUSE:HPE Helion OpenStack 8	python-Django	before 1.11.23-3.12.1	1.11.23-3.12.1
SUSE:OpenStack Cloud 7	python-Django	before 1.8.19-3.15.1	1.8.19-3.15.1
SUSE:OpenStack Cloud 9	python-Django1	before 1.11.23-3.9.1	1.11.23-3.9.1
SUSE:Package Hub 15 SP1	python-Django	before 2.2.4-bp151.3.3.1	2.2.4-bp151.3.3.1

Same product

djangoproject: all records

Other highest-scoring records for the same primary product.

CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
61This week
CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter…
59Plan
CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
55Plan

Published before and after this one in the same product

← EarlierCVE-2019-12781Jul 1, 2019 · An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3.
22Monitor
← EarlierCVE-2019-14232Aug 2, 2019 · 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.
31Monitor
Later →CVE-2019-14235Aug 2, 2019 · 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.
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
alpine:py-django	1.11.23-r0 · Alpine:v3.10	Package registry (OSV)
alpine:py3-django	1.11.23-r0 · Alpine:v3.11	Package registry (OSV)
debian:python-django	2:2.2.4-1 · Debian:12	Package registry (OSV)
opensuse:python-Django	2.2.4-lp151.2.3.1 · openSUSE:Leap 15.1	Package registry (OSV)
PyPI:django	1.11.23	Package registry (OSV)
PyPI:django	2.1.11	Package registry (OSV)
PyPI:django	2.2.4	Package registry (OSV)
red hat:python-django	0:2.1.11-1.el8ost · Red Hat:openstack:15::el8	Package registry (OSV)
red hat:python-django-bash-completion	0:2.1.11-1.el8ost · Red Hat:openstack:15::el8	Package registry (OSV)
red hat:python2-django	0:1.11.27-1.el7ost · Red Hat:openstack:13::el7	Package registry (OSV)
red hat:python3-django	0:2.1.11-1.el8ost · Red Hat:openstack:15::el8	Package registry (OSV)
suse:python-Django	1.8.19-3.15.1 · SUSE:OpenStack Cloud 7	Package registry (OSV)
suse:python-Django1	1.11.23-3.9.1 · SUSE:OpenStack Cloud 9	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-20-301 · May 4, 2020(Django Güvenlik Güncellemesi Yayınladı)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records