RUSTSEC-2026-0387: Multiple timing variability issues in operations intended to be constant-time
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 1/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Rust
- Estrellas
- 2
- Forks
- 2
- Merge medio
- 13 h 13 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DiamondLightSource/numtracker
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
DiamondLightSource/numtracker#309 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
DiamondLightSource/numtracker#278 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
DiamondLightSource/numtracker#329 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 20/100
DiamondLightSource/numtracker#326 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
DiamondLightSource/numtracker#325 ·
Todos los issues de DiamondLightSource/numtracker
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Non-`main` default branchesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
max-sixty/worktrunk#4727 · 7 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
carrick-sh/carrick#1859 ·
Los mantenedores suelen responder en 1 día
-
crate: spate-kafka documentation priority: medium
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día