#36470: Potential log injection in development server (runserver) logging
-------------------------------------+-------------------------------------
Reporter: Natalia Bidart | Owner:
Type: | YashRaj1506
Cleanup/optimization | Status: closed
Component: Core (Management | Version: dev
commands) |
Severity: Normal | Resolution: fixed
Keywords: runserver | Triage Stage: Accepted
log_message |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"f5b6ed78200b2cbff71ec771e6f014de5d4abbd8" f5b6ed78]:
{{{#!CommitTicketReference repository=""
revision="f5b6ed78200b2cbff71ec771e6f014de5d4abbd8"
[6.0.x] Fixed #36470 -- Prevented log injection in runserver when handling
NOT FOUND.
Migrated `WSGIRequestHandler.log_message()` to use a more robust
`log_message()` helper, which was based of `log_response()` via factoring
out
the common bits.
Refs CVE-2025-48432.
Co-authored-by: Natalia <[email protected]>
Backport of 9bb83925d6c231e964f8b54efbc982fb1333da27 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36470#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a0312d157-6b401ead-78d9-42c6-a1a2-06b994a28ebc-000000%40eu-central-1.amazonses.com.
