RUSTSEC-2026-0097: Rand is unsound with a custom logger using `rand::rng()`
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading the linked rand advisory at https://github.com/rust-random/rand/pull/1763 and check how this repository depends on or configures rand. The report describes undefined behavior in rand under specific logger and feature conditions but does not say what change this repository should make. Done is unclear from the issue text alone.
由索引模型根据 Issue 内容生成。
描述
| Details | |
|---|---|
| Package | rand |
| Version | 0.8.5 |
| Warning | unsound |
| URL | https://github.com/rust-random/rand/pull/1763 |
| Patched Versions | >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 |
| Unaffected Versions | <0.7.0 |
| Aliases | GHSA-cq8v-f236-94qc |
It has been reported (by @lopopolo) that the rand library is unsound (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
- The
logandthread_rngfeatures are enabled - A custom logger is defined
- The custom logger accesses
rand::rng()(previouslyrand::thread_rng()) and calls anyTryRng(previouslyRngCore) methods onThreadRng - The
ThreadRng(attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data) - Trace-level logging is enabled or warn-level logging is enabled and the random source (the
getrandomcrate) is unable to provide a new seed
TryRng (previously RngCore) methods for ThreadRng use unsafe code to cast *mut BlockRng<ReseedingCore> to &mut BlockRng<ReseedingCore>. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of aliased mutable references is Undefined Behaviour, the behaviour of optimized builds is hard to predict.
- 主要语言
- Rust
- 星标
- 10
- 派生
- 8
- 平均合并
- 11 天 12 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
bitcoindevkit/electrum_streaming_client 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
bitcoindevkit/electrum_streaming_client#57 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
bitcoindevkit/electrum_streaming_client#56 ·
维护者通常 2 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 78/100
bitcoindevkit/electrum_streaming_client#29 ·
维护者通常 2 天内回复
-
RUSTSEC-2026-0221: `event-listener` allows `!Send` tags to cross thread boundaries via `StackSlot`未关闭
难度 2/5 1-3 小时 新手友好度 51/100
bitcoindevkit/electrum_streaming_client#54 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 1/100
bitcoindevkit/electrum_streaming_client#53 ·
维护者通常 2 天内回复
查看 bitcoindevkit/electrum_streaming_client 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
farion1231/cc-switch#8829 · 1 条评论 ·
维护者通常 1 天内回复
-
Validate CI command vectors before indexing Cargo subcommands可能已有人在做 @amandeavor 今天认领。 未关闭bug ci good first issue
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
longbridge/gpui-kit#3677 ·
维护者通常 1 天内回复
-
E-pr-welcome
难度 2/5 1-3 小时 新手友好度 77/100
seanmonstar/reqwest#3121 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
ilya-zlobintsev/LACT#1235 ·
维护者通常 1 天内回复