RUSTSEC-2026-0349: Unauthenticated ServerHello can downgrade later connections to classical key exchange
还没有人认领这个 Issue。
评估
调研方向
该 issue 要求将 rustls 依赖从 0.23.45 升级到至少 0.23.46，即安全公告中指明的修复版本。先查看 Cargo 清单和锁文件，确定 rustls 在哪里被固定，然后阅读 issue 中链接的安全公告页面以了解确切的修复内容。完成标准是解析后的 rustls 版本为 0.23.46 或更高，且项目能够构建并通过测试。
由索引模型根据 Issue 内容生成。
描述
Unauthenticated ServerHello can downgrade later connections to classical key exchange
| Details | |
|---|---|
| Package | rustls |
| Version | 0.23.45 |
| URL | https://github.com/rustls/rustls/pull/3355 |
| Date | 2026-10-14 |
| Patched versions | >=0.23.46 |
The client recorded the server-selected key exchange group for each server
name when processing the ServerHello, before the server was authenticated.
This record is used to predict which key share to send in future ClientHellos
to that server name.
A network attacker can answer one connection attempt with a ServerHello
selecting X25519, and then close the connection. Later ClientHellos for that
name carry only an X25519 key share, while supported_groups still lists
X25519MLKEM768 first. If the genuine server accepts that share rather than
sending a HelloRetryRequest for its preferred hybrid group, the handshake
completes with classical-only key exchange and no error. This persists for as
long as the entry stays in the client's session store.
The impact is loss of post-quantum confidentiality for affected connections
("harvest now, decrypt later"). There is no key compromise and no
authentication bypass.
The following are not affected:
- connections to servers which send a HelloRetryRequest for their preferred group,
- clients with resumption disabled (as nothing is stored), and
- other server names.
This behaviour is discussed in
draft-ietf-tls-key-share-prediction,
so the practical impact depends largely on server policy.
See advisory page for additional details.
- 主要语言
- Rust
- 星标
- 11
- 派生
- 5
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stackabletech/stackablectl 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 65/100
stackabletech/stackablectl#475 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
stackabletech/stackablectl#471 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
stackabletech/stackablectl#456 ·
-
难度 1/5 1 小时以内 新手友好度 35/100
stackabletech/stackablectl#476 ·
-
难度 2/5 1-3 小时 新手友好度 45/100
stackabletech/stackablectl#474 ·
查看 stackabletech/stackablectl 的全部 Issue
相似的 Issue
-
yara-x fails to build with rsa 0.10.0: unresolved import rsa::Pkcs1v15Sign可能已有人在做 @CfirTsabari 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 87/100
VirusTotal/yara-x#865 ·
维护者通常 1 天内回复
-
good first issue help wanted program
难度 2/5 1-3 小时 新手友好度 83/100
hffgzktbcc-blip/ounce-core#297 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
nautechsystems/nautilus_trader#5631 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
bytecodealliance/rustix#1736 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
longbridge/gpui-kit#3871 ·
维护者通常 1 天内回复