RUSTSEC-2026-0349: Unauthenticated ServerHello can downgrade later connections to classical key exchange
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The report identifies the affected dependency as rustls 0.23.45 and links rustls pull request 3355; it does not name files or tests in sentry-rust. Start by checking how this SDK pins and configures rustls, then review the linked fix and advisory details. Done means the affected dependency behavior is addressed and relevant checks confirm the fix.
由索引模型根据 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
- 星标
- 755
- 派生
- 192
- 平均合并
- 3 天 15 小时
- 30 天内合并 PR
- 12
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
getsentry/sentry-rust 的其他 Issue
-
breaking change
难度 2/5 1-3 小时 新手友好度 65/100
getsentry/sentry-rust#1387 · 1 条评论 ·
维护者通常 1 天内回复
-
breaking change Rust
难度 2/5 1-3 小时 新手友好度 68/100
getsentry/sentry-rust#1386 · 1 条评论 ·
维护者通常 1 天内回复
-
`Transport::flush` on an `Arc<T>` transport returns `true` without flushing `T`可能已有人在做 @sentry-junior 于 3 天前认领。 未关闭Bug Rust
难度 1/5 1 小时以内 新手友好度 85/100
getsentry/sentry-rust#1374 · 2 条评论 ·
维护者通常 1 天内回复
-
breaking change Rust Task
难度 2/5 1-3 小时 新手友好度 65/100
getsentry/sentry-rust#1345 · 1 条评论 ·
维护者通常 1 天内回复
-
Rust Task
难度 2/5 1-3 小时 新手友好度 62/100
getsentry/sentry-rust#933 · 1 条评论 ·
维护者通常 1 天内回复
查看 getsentry/sentry-rust 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
go good first issue
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
-
[Python] Worker.close() spins at 100% CPU when its teardown task is canceled可能已有人在做 @Glutexo 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
taskforcesh/bullmq#5053 ·
维护者通常 1 天内回复
-
Cloud environment origin check accepts an explicit default HTTPS port (:443) (follow-up to #30418)未关闭area: cloud
难度 2/5 1-3 小时 新手友好度 70/100
manaflow-ai/cmux#31340 · 1 条评论 ·
维护者通常 1 天内回复