Descripción
An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14.
ASGI requests with a missing or understated `Content-Length` header can bypass the `FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading large files into memory and causing service degradation.
As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on `FILE_UPLOAD_MAX_MEMORY_SIZE`.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Kyle Agronick for reporting this issue.
Datos: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Se publican tal como los indican las fuentes, en inglés.
Productos y versiones afectados
| Fabricante | Producto | Versiones | |
| djangoproject |
Django |
6.0 – < 6.0.5, fixed 6.0.5, 5.2 – < 5.2.14, fixed 5.2.14 |
|
Coincidencias CPE (NVD) (2)
cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:* ≥ 5.2 < 5.2.14cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:* ≥ 6.0 < 6.0.5