Deps.rs

deno_crypto 0.191.0

[![dependency status](https://deps.rs/crate/deno_crypto/0.191.0/status.svg)](https://deps.rs/crate/deno_crypto/0.191.0)

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

Crate deno_crypto

Dependencies

(31 total, 5 outdated, 1 insecure)

CrateRequiredLatestStatus
 aes=0.8.30.8.4out of date
 aes-gcm^0.100.10.3up to date
 aes-kw^0.2.10.2.1up to date
 base64^0.21.70.22.1out of date
 cbc=0.1.20.1.2up to date
 const-oid^0.9.00.9.6up to date
 ctr^0.9.10.9.2up to date
 curve25519-dalek^4.1.34.1.3up to date
 deno_core^0.318.00.319.0out of date
 deno_web^0.208.00.208.0up to date
 ed448-goldilocks^0.8.30.9.0out of date
 elliptic-curve^0.13.10.13.8up to date
 num-traits^0.2.140.2.19up to date
 once_cell^1.17.11.20.2up to date
 p256^0.13.20.13.2up to date
 p384^0.13.00.13.0up to date
 p521^0.13.30.13.3up to date
 rand=0.8.50.8.5up to date
 ring^0.17.00.17.8up to date
 rsa ⚠️^0.9.30.9.6insecure
 sec1^0.70.7.3up to date
 serde^1.0.1491.0.215up to date
 serde_bytes^0.110.11.15up to date
 sha1^0.10.60.10.6up to date
 sha2^0.10.80.10.8up to date
 signature^2.12.2.0up to date
 spki^0.7.20.7.3up to date
 thiserror^1.0.612.0.3out of date
 tokio^1.36.01.41.1up to date
 uuid^1.3.01.11.0up to date
 x25519-dalek^2.0.02.0.1up 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.