CVE-2019-14235

medium
Published 2019-08-06 ยท Modified 2023-11-08
CVSS v3
โ€”
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
5.5

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. If passed certain inputs, django.utils.encoding.uri_to_iri could lead to significant memory usage due to a recursion when repercent-encoding invalid UTF-8 octet sequences.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

suse SUSE Affected 1 release
VersionStatusFixed in
โ€” Affected โ€”
arch Arch Fixed 1 release
VersionStatusFixed in
โ€” Fixed 2.2.4-1
debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 2:2.2.4-1
sid Fixed 2:2.2.4-1
forky Fixed 2:2.2.4-1
bullseye Fixed 2:2.2.4-1
bookworm Fixed 2:2.2.4-1

Package impact

EcosystemPackageVulnerableFixed
python PyPIdjango>=1.11a1,<1.11.231.11.23
python PyPIdjango>=2.1a1,<2.1.112.1.11
python PyPIdjango>=2.2a1,<2.2.42.2.4
python PyPIdjango>=2.1,<2.1.112.2.4

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.