fix(deps): update rust crate tungstenite to 0.20.0 [security] #18
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:
0.18.0
->0.20.0
GitHub Vulnerability Alerts
CVE-2023-43669
The Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).
Release Notes
snapview/tungstenite-rs (tungstenite)
v0.20.1
Compare Source
v0.20.0
Compare Source
longer flush until calling
flush
. An exception is automatic responses (e.g. pongs)which will continue to be written and flushed when reading and writing.
This allows writing a batch of messages and flushing once, improving performance.
WebSocket::read
,write
,send
,flush
. Deprecateread_message
,write_message
,write_pending
.FrameSocket::read
,write
,send
,flush
. Removeread_frame
,write_frame
,write_pending
.Note: Previous use of
write_frame
may be replaced withsend
.WebSocketContext::read
,write
,flush
. Removeread_message
,write_message
,write_pending
.Note: Previous use of
write_message
may be replaced withwrite
+flush
.send_queue
, replaced with using the frame write buffer to achieve similar results.WebSocketConfig::max_write_buffer_size
. Deprecatemax_send_queue
.Error::WriteBufferFull
. RemoveError::SendQueueFull
.Note:
WriteBufferFull
returns the message that could not be written as aMessage::Frame
.WebSocketConfig::write_buffer_size
(default 128 KiB). Improves batch message write performance.WebSocketConfig
.v0.19.0
Compare Source
base64
fordata-encoding
.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 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.