Deps.rs

deno_node 0.135.0

[![dependency status](https://deps.rs/crate/deno_node/0.135.0/status.svg)](https://deps.rs/crate/deno_node/0.135.0)

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

Crate deno_node

Dependencies

(80 total, 7 outdated, 1 insecure)

CrateRequiredLatestStatus
 aead-gcm-stream^0.40.4.0up to date
 aes=0.8.30.8.4out of date
 base64^0.22.10.22.1up to date
 blake2^0.10.60.10.6up to date
 boxed_error^0.2.30.2.3up to date
 brotli^6.0.07.0.0out of date
 bytes^1.4.01.10.1up to date
 cbc=0.1.20.1.2up to date
 const-oid^0.9.50.10.0out of date
 ctr^0.9.20.9.2up to date
 data-encoding^2.3.32.8.0up to date
 deno_core^0.341.00.341.0up to date
 deno_error=0.5.60.5.6up to date
 deno_fetch^0.221.00.221.0up to date
 deno_fs^0.107.00.107.0up to date
 deno_io^0.107.00.107.0up to date
 deno_net^0.189.00.189.0up to date
 deno_package_json=0.6.00.6.0up to date
 deno_path_util=0.3.20.3.2up to date
 deno_permissions^0.56.00.56.0up to date
 deno_process^0.12.00.12.0up to date
 deno_whoami^0.1.00.1.0up to date
 der^0.7.90.7.9up to date
 digest^0.10.50.10.7up to date
 dsa^0.6.30.6.3up to date
 ecb=0.1.20.1.2up to date
 ecdsa^0.16.90.16.9up to date
 ed25519-dalek^2.1.12.1.1up to date
 elliptic-curve^0.13.40.13.8up to date
 errno^0.3.100.3.10up to date
 faster-hex^0.10.00.10.0up to date
 h2^0.4.60.4.8up to date
 hkdf^0.12.30.12.4up to date
 http^1.01.3.1up to date
 http-body-util^0.1.20.1.3up to date
 hyper^1.6.01.6.0up to date
 hyper-util^0.1.100.1.11up to date
 idna^1.0.31.0.3up to date
 ipnetwork^0.20.00.21.1out of date
 k256^0.13.10.13.4up to date
 libc^0.2.1680.2.171up to date
 libz-sys^1.1.201.1.22up to date
 md-5^0.10.50.10.6up to date
 md4^0.10.20.10.2up to date
 node_resolver^0.35.00.35.0up to date
 num-bigint^0.40.4.6up to date
 num-bigint-dig^0.8.20.8.4up to date
 num-integer^0.1.450.1.46up to date
 num-traits^0.2.190.2.19up to date
 once_cell^1.17.11.21.3up to date
 p224^0.13.00.13.2up to date
 p256^0.13.20.13.2up to date
 p384^0.13.00.13.1up to date
 pbkdf2^0.12.10.12.2up to date
 pkcs8^0.10.20.10.2up to date
 rand=0.8.50.9.0out of date
 ring^0.17.140.17.14up to date
 ripemd^0.1.30.1.3up to date
 rsa ⚠️^0.9.30.9.8insecure
 rusqlite^0.34.00.34.0up to date
 scrypt^0.11.00.11.0up to date
 sec1^0.70.7.3up to date
 serde^1.0.1491.0.219up to date
 sha1^0.10.60.10.6up to date
 sha2^0.10.80.10.8up to date
 sha3^0.10.80.10.8up to date
 signature^2.12.2.0up to date
 sm3^0.4.20.4.2up to date
 spki^0.7.20.7.3up to date
 sys_traits=0.1.80.1.8up to date
 thiserror^2.0.122.0.12up to date
 tokio^1.36.01.44.1up to date
 tokio-eld^0.20.2.0up to date
 url^2.52.5.4up to date
 webpki-root-certs^0.26.50.26.8up to date
 winapi=0.3.90.3.9up to date
 windows-sys^0.59.00.59.0up to date
 x25519-dalek^2.0.02.0.1up to date
 x509-parser^0.15.00.17.0out of date
 yoke^0.7.40.8.0out of 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.