Django Improper Output Neutralization for Logs vulnerability
djangoproject Django
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
djangoproject Django
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems.
From the CVE record · mitre
Django’s internal HTTP response logging does not escape request paths. A remote attacker can use crafted URLs to potentially inject or forge log entries when logs are viewed in terminals or processed by external systems; authentication and user-interaction requirements are not specified.
Engineers running Django 4.2, 5.1, or 5.2 should check their versions against the affected ranges in the advisory.