Django contains Uncontrolled Resource Consumption via cached header
In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-service vector via excessive memory usage if the raw value of Accept-Language headers is very large.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-23969US | high7.5 | — | ||
In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a p… | ||||
02
references
External citations — patches, advisories, analysis.
- https://docs.djangoproject.com/en/4.1/releases/securityWEB
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/4452642f193533e288a52c02efb5bbc766a68f95WEB
- https://github.com/django/django/commit/9d7bd5a56b1ce0576e8e07a8001373576d277942WEB
- https://github.com/django/django/commit/c7e0151fdf33e1b11d488b6f67b94fdf3a30614aWEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2023-12.yamlWEB
- https://groups.google.com/forum/#!forum/django-announceWEB
- https://lists.debian.org/debian-lts-announce/2023/02/msg00000.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan