RUSTSEC-2026-0387: Multiple timing variability issues in operations intended to be constant-time
还没有人认领这个 Issue。
评估
调研方向
The issue describes a security advisory for crypto-bigint and points to the upstream pull request and advisory page; it names no files or tests in this repository. Read those references first to understand the affected operations and upgrade guidance. Done would mean identifying and addressing whether numtracker uses the affected package version; the issue does not specify a concrete change or validation target.
由索引模型根据 Issue 内容生成。
描述
Multiple timing variability issues in operations intended to be constant-time
| Details | |
|---|---|
| Package | crypto-bigint |
| Version | 0.5.5 |
| URL | https://github.com/RustCrypto/crypto-bigint/pull/1365 |
| Date | 2026-10-23 |
| Patched versions | >=0.7.6 |
Summary
Several operations intended to be constant-time could execute secret-dependent
branches, depending on the compiler and target CPU. These include subtraction,
zero counting, division, and Montgomery multiplication.
Additionally, UintRef equality could terminate at the first unequal limb,
and BoxedMontyForm::invert branched on whether an inverse exists.
Impact
Applications using affected operations on secret integers may leak information
through timing or microarchitectural side channels. This includes information
about intermediate arithmetic values, matching limbs, and invertibility.
Such leakage could potentially enable recovery of cryptographic secrets.
Practical exploitability depends on the downstream algorithm, compiler, target
CPU, and an attacker's ability to observe the side channel.
Resolution
Upgrade to v0.7.6, which removes the identified branches, updates ctutils to
include its constant-time fixes, and adds BINSEC-based regression checks using
cargo checkct for arithmetic on multiple targets.
See advisory page for additional details.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 2
- 平均合并
- 13 小时 13 分钟
- 30 天内合并 PR
- 5
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DiamondLightSource/numtracker 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 70/100
DiamondLightSource/numtracker#309 ·
-
难度 1/5 1 小时以内 新手友好度 82/100
DiamondLightSource/numtracker#278 ·
-
难度 2/5 1-3 小时 新手友好度 45/100
DiamondLightSource/numtracker#329 ·
-
难度 1/5 1 小时以内 新手友好度 20/100
DiamondLightSource/numtracker#326 ·
-
难度 4/5 3-5 天 新手友好度 20/100
DiamondLightSource/numtracker#325 ·
查看 DiamondLightSource/numtracker 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
max-sixty/worktrunk#4727 · 7 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
follow-up
难度 2/5 1-3 小时 新手友好度 73/100
carrick-sh/carrick#1859 ·
维护者通常 1 天内回复
-
crate: spate-kafka documentation priority: medium
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复