Deps.rs

vemonet / nanopub-rs

[![dependency status](https://deps.rs/repo/github/vemonet/nanopub-rs/status.svg)](https://deps.rs/repo/github/vemonet/nanopub-rs)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate nanopub

Dependencies

(10 total, 1 insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 rsa ⚠️^0.9.60.9.6insecure
 openssl-probe^0.10.1.5up to date
 sophia^0.8.00.8.0up to date
 regex^1.101.10.4up to date
 serde^1.01.0.201up to date
 chrono^0.4.350.4.38up to date
 getrandom^0.20.2.15up to date
 rand_core^0.60.6.4up to date
 reqwest^0.120.12.4up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 wasm-pack^0.12.10.12.1up to date
 tokio^1.361.37.0up to date

Crate nanopub-cli

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 clap^4.54.5.4up to date
 clap_complete^4.54.5.2up to date
 tokio^1.361.37.0up to date

Crate nanopub-sign

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 pyo3^0.210.21.2up to date
 pythonize^0.210.21.1up to date
 tokio^1.361.37.0up to date

Crate nanopub-js

Dependencies

(7 total, all up-to-date)

CrateRequiredLatestStatus
 wasm-bindgen^0.20.2.92up to date
 wasm-bindgen-futures^0.40.4.42up to date
 wasm-bindgen-derive^0.20.2.1up to date
 js-sys^0.30.3.69up to date
 console_error_panic_hook^0.10.1.7up to date
 serde^1.01.0.201up to date
 serde-wasm-bindgen^0.60.6.5up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 wasm-bindgen-test^0.30.3.42up to date

Security Vulnerabilities

rsa: Marvin Attack: potential key recovery through timing sidechannels

RUSTSEC-2023-0071

Impact

Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.

Patches

No patch is yet available, however work is underway to migrate to a fully constant-time implementation.

Workarounds

The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.

References

This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.