chore(deps): bump quinn-proto from 0.11.14 to 0.11.17 in the cargo group across 1 directory

[dependabot]

Bumps the cargo group with 1 update in the / directory: quinn-proto.

Updates quinn-proto from 0.11.14 to 0.11.17

Release notes

Sourced from quinn-proto's releases.

quinn-proto 0.11.17

This release fixes three remote memory exhaustion issues. See GHSA-qfwj-vfxf-92j2, GHSA-2hv7-gw8g-gpq5, and GHSA-hmxj-32vh-65vr for more details, and quinn-rs/quinn#2789 for the fixes.

What's Changed

• fix(ci): fix clippy lints by @​LesnyRumcajs in quinn-rs/quinn#2752
• congestion: saturate CUBIC window increment to avoid overflow by @​LesnyRumcajs in quinn-rs/quinn#2751
• 0.11.x: Backport memory use fixes and prepare release by @​Ralith in quinn-rs/quinn#2790

Full Changelog: quinn-rs/quinn@quinn-proto-0.11.16...quinn-proto-0.11.17

quinn-proto-0.11.16

What's Changed

• 0.11.x: upgrade dependencies by @​djc in quinn-rs/quinn#2707

quinn-proto 0.11.15, quinn 0.11.11

This release fixes a remote memory exhaustion issue in the quinn-proto Assembler. See GHSA-4w2j-m93h-cj5j for more details and #2694 for the fix.

Two sponsoring organizations participated in coordinated disclosure. If this is relevant to your organization, please contact us to keep support Quinn maintenance.

What's Changed

• Prepare 0.11.x branch for release by @​djc in quinn-rs/quinn#2645
• Backport of #2495 to 0.11.x by @​stablebits in quinn-rs/quinn#2674
• 0.11.x backport | quinn-proto: drop Initials silently when saturated by @​stablebits in quinn-rs/quinn#2688
• Backport #2677 to 0.11.x by @​syszery in quinn-rs/quinn#2690
• congestion: avoid double-reducing CUBIC fast convergence (0.11.x) by @​0xdeafbeef in quinn-rs/quinn#2641
• proto: yield error on too many gaps in assembler by @​djc in quinn-rs/quinn#2694

Commits

• 0343120 proto: bump version to 0.11.17
• d7bf3d0 Limit total memory used to buffer outgoing datagrams
• 31ca5d2 Limit total memory used to buffer incoming datagrams
• 3a78b60 Factor out DatagramBuffer for queues in either direction
• b37ced3 proto: check limits when processing already retired CIDs
• 6a984b8 proto: extract method for checking CID retirements
• 499dba8 proto: bound assembler chunk count regardless of over-allocation
• 33ce0c2 congestion: saturate CUBIC window increment to avoid overflow
• c8ad7e6 fix(ci): fix clippy lints
• a96949f Take semver-compatible update for anyhow
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[open-cla]

Contributor License Agreement

All contributors are covered by a CLA.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Recently published: cargo chacha20 published 22 hours ago Location: Package overview From: ? → cargo/rig-core@0.28.0 → cargo/reqwest@0.13.2 → cargo/rustsec@0.31.0 → cargo/chacha20@0.10.2 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/chacha20@0.10.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Recently published: cargo cpufeatures published 2 days ago Location: Package overview From: ? → cargo/rig-core@0.28.0 → cargo/reqwest@0.13.2 → cargo/rustsec@0.31.0 → cargo/cpufeatures@0.3.1 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/cpufeatures@0.3.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report