Update dependency daphne to v4.2.2#71
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
e7a966c to
46246af
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==4.2.0→==4.2.2Release Notes
django/daphne (daphne)
v4.2.2Compare Source
Fixed a denial of service vulnerability via unbounded WebSocket message sizes.
Daphne previously passed no message or frame size limits to autobahn,
whose defaults are unbounded. This allowed an unauthenticated client
to exhaust server memory by sending a very large WebSocket
messages/frames (CVE-2026-44545).
Both limits now default to 1 MiB and can be configured via the new
--websocket-max-message-sizeand--websocket-max-frame-sizeCLIflags (or the matching
Serverconstructor arguments). Pass0torestore the previous unlimited behaviour.
Thanks to ParkHyunWoo for the report.
Fixed a header injection vulnerability on the WebSocket upgrade path
(CVE-2026-44546).
Header values containing
\x0b,\x0c,\x1c,\x1d,\x1e,or
\x85were parsed as a single header by Twisted but split intomultiple headers by autobahn during the WebSocket handshake. An attacker
could exploit this parser differential to smuggle additional headers
(e.g. authentication tokens,
X-Forwarded-For,Origin,Daphne-Root-Path) into the ASGI scope passed to the application.Daphne now rejects requests carrying these bytes in any header value with
a 400 Bad Request response, as required by RFC 9110 §5.5.
Thanks to Rene Henningsen for the report.
v4.2.1Compare Source
Fixed a packaging error in 4.2.0.
Removed --nostatic and --insecure args to runserver command when staticfiles
app is not installed.
Configuration
📅 Schedule: (in timezone Etc/UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.