Opened 3 months ago
Last modified 2 months ago
#36470 assigned Cleanup/optimization
Potential log injection in development server (runserver) logging — at Initial Version
| Reported by: | Natalia Bidart | Owned by: | |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | runserver log_message |
| Cc: | Jake Howard | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
django.core.servers.basehttp.WSGIRequestHandler.log_response() may emit log records that are not properly escaped or sanitized, making it possible for specially crafted requests to inject terminal escape sequences or misleading log content. This only affects the internal development server (runserver command). Per the documentation, this server is not intended for production use and has not been security-audited.
Although this is not considered a vulnerability, a fix for defense-in-depth should be applied, also to avoid confusion and future security reports about the same thing. This fix would be in line to what Python does for esacaping.
Thanks to "Kainan Zhang (@4xpl0r3r) from Fortinet" for the report in the security mailing list.