Deps.rs

sorah / needroleshere

[![dependency status](https://deps.rs/repo/github/sorah/needroleshere/status.svg)](https://deps.rs/repo/github/sorah/needroleshere)

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

Crate needroleshere

Dependencies

(40 total, 5 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.751.0.82up to date
 async-trait^0.1.740.1.80up to date
 axum^0.6.200.7.5out of date
 base16ct^0.2.00.2.0up to date
 base64ct^1.6.01.6.0up to date
 bytes^1.5.01.6.0up to date
 chrono^0.4.310.4.38up to date
 clap^3.2.224.5.4out of date
 crypto-bigint^0.5.30.5.5up to date
 digest^0.10.50.10.7up to date
 ecdsa^0.16.80.16.9up to date
 elliptic-curve^0.13.60.13.8up to date
 generic-array^1.0.01.0.0up to date
 headers^0.3.90.4.0out of date
 http^0.2.91.1.0out of date
 listenfd^1.0.01.0.1up to date
 num-bigint^0.4.30.4.4up to date
 once_cell^1.18.01.19.0up to date
 p256^0.13.20.13.2up to date
 p384^0.13.00.13.0up to date
 pem-rfc7468^0.7.00.7.0up to date
 pkcs1^0.7.50.7.5up to date
 pkcs8^0.10.20.10.2up to date
 rand^0.8.50.8.5up to date
 regex^1.6.01.10.4up to date
 reqwest^0.11.220.12.4out of date
 rfc6979^0.4.00.4.0up to date
 rsa ⚠️^0.9.30.9.6insecure
 sec1^0.7.30.7.3up to date
 secrecy^0.8.00.8.0up to date
 serde^1.0.1901.0.198up to date
 serde_json^1.0.1081.0.116up to date
 sha2^0.10.80.10.8up to date
 thiserror^1.0.501.0.59up to date
 tokio^1.33.01.37.0up to date
 tracing^0.1.400.1.40up to date
 tracing-subscriber^0.3.170.3.18up to date
 url^2.4.12.5.0up to date
 x509-cert^0.2.40.2.5up to date
 zeroize^1.6.01.8.0up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 hyper^0.14.271.3.1out of date
 indoc^2.0.42.0.5up to date
 openssl^0.10.590.10.64up to date
 temp-dir^0.1.110.1.13up to date
 tower^0.4.130.4.13up 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.