Deps.rs

igankevich / zar

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

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

Crate zar

Dependencies

(17 total, 1 insecure)

CrateRequiredLatestStatus
 base16ct^0.2.00.2.0up to date
 base64ct^1.6.01.7.3up to date
 bzip2^0.5.10.5.2up to date
 chrono^0.4.390.4.40up to date
 deko^0.4.00.4.0up to date
 digest^0.10.70.10.7up to date
 flate2^1.0.351.1.0up to date
 libc^0.2.1690.2.171up to date
 md5^0.7.00.7.0up to date
 normalize-path^0.2.10.2.1up to date
 quick-xml^0.37.20.37.2up to date
 rsa ⚠️^0.9.70.9.8insecure
 serde^1.0.2171.0.219up to date
 sha1^0.10.60.10.6up to date
 sha2^0.10.80.10.8up to date
 x509-cert^0.2.50.2.5up to date
 xz^0.1.00.1.0up to date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 arbitrary^1.4.11.4.1up to date
 arbtest^0.3.20.3.2up to date
 random-dir^0.2.40.2.4up to date
 similar-asserts^1.6.11.7.0up to date
 tempfile^3.16.03.19.1up to date
 x509-cert^0.2.50.2.5up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 x509-cert^0.2.50.2.5up to date

Crate zar-cli

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 clap^4.5.294.5.32up to date
 libc^0.2.1690.2.171up to date
 x509-cert^0.2.50.2.5up to date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 arbitrary^1.4.11.4.1up to date
 arbtest^0.3.20.3.2up to date
 random-dir^0.2.40.2.4up to date
 similar-asserts^1.6.11.7.0up to date
 tempfile^3.16.03.19.1up to date
 test_bin^0.4.00.4.0up 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.