RUSTSEC-2026-0339: Unbounded growth of pending connection ID retirements in quinn-proto
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 20/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- rust
- 领域
- networking, security
调研方向
The report describes an already corrected vulnerability in quinn-proto 0.11.17, with the affected path in NEW_CONNECTION_ID processing. Read the linked advisory and pull request for the fix details, then check whether this repository uses an affected quinn-proto version; done means confirming the dependency is patched or identifying a specific remaining update.
由索引模型根据 Issue 内容生成。
描述
Unbounded growth of pending connection ID retirements in quinn-proto
| Details | |
|---|---|
| Package | quinn-proto |
| Version | 0.11.16 |
| URL | https://github.com/quinn-rs/quinn/pull/2790 |
| Date | 2026-08-17 |
| Patched versions | >=0.11.17 |
| Unaffected versions | <0.6.0 |
When processing a NEW_CONNECTION_ID frame, quinn-proto queues a RETIRE_CONNECTION_ID frame for
each connection ID that the peer asked it to retire. The normal path bounds this queue and closes
the connection with a CONNECTION_ID_LIMIT_ERROR if the bound would be exceeded. However, the path
handling a connection ID that had already been retired pushed onto the queue without applying
the limit and without deduplicating.
A peer that has completed the handshake can first send a NEW_CONNECTION_ID frame with a large
retire_prior_to value to advance the receiver's connection ID window, and then repeatedly send
NEW_CONNECTION_ID frames with sequence numbers below that window. Each such frame adds another
entry to the queue. The queue is only drained by sending RETIRE_CONNECTION_ID frames, which are
subject to congestion control, so a peer that withholds acknowledgements can stall the drain while
continuing to flood, growing the victim's memory use without bound.
The flaw was corrected in 0.11.17 by applying the same limit on the already-retired path.
Thanks to @scadastrangelove for reporting this issue.
See advisory page for additional details.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 1 天 15 小时
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stackabletech/stackable-odbc-trino 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 62/100
-
难度 1/5 1 小时以内 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 55/100
-
RUSTSEC-2026-0348: Brotli certificate decompression can allocate up to 1 GiB before authentication未关闭
难度 2/5 1-3 小时 新手友好度 50/100
-
难度 5/5 一周以上 新手友好度 15/100
查看 stackabletech/stackable-odbc-trino 的全部 Issue
相似的 Issue
-
area:io needs-info needs-triage
难度 2/5 1-3 小时 新手友好度 63/100
bherbruck/solvecraft#3216 · 1 条评论 ·
-
bug triage/needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
praxis-proxy/grid#412 ·
维护者通常 1 天内回复
-
priority: low
难度 2/5 1-3 小时 新手友好度 63/100
storytold/photocraft#7824 · 1 条评论 ·
维护者通常 1 天内回复
-
area:ui chore could help wanted
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复