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

Crate needroleshere

Dependencies

(40 total, 9 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.751.0.95up to date
 async-trait^0.1.740.1.86up to date
 axum^0.6.200.8.1out of date
 base16ct^0.2.00.2.0up to date
 base64ct^1.6.01.6.0up to date
 bytes^1.5.01.10.0up to date
 chrono^0.4.310.4.39up to date
 clap^3.2.224.5.28out of date
 crypto-bigint^0.5.30.6.0out of 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.2.0up to date
 headers^0.3.90.4.0out of date
 http^0.2.91.2.0out of date
 listenfd^1.0.01.0.2up to date
 num-bigint^0.4.30.4.6up to date
 once_cell^1.18.01.20.3up to date
 p256^0.13.20.13.2up to date
 p384^0.13.00.13.1up 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.9.0out of date
 regex^1.6.01.11.1up to date
 reqwest^0.11.220.12.12out of date
 rfc6979^0.4.00.4.0up to date
 rsa ⚠️^0.9.30.9.7insecure
 sec1^0.7.30.7.3up to date
 secrecy^0.8.00.10.3out of date
 serde^1.0.1901.0.217up to date
 serde_json^1.0.1081.0.138up to date
 sha2^0.10.80.10.8up to date
 thiserror^1.0.502.0.11out of date
 tokio^1.33.01.43.0up to date
 tracing^0.1.400.1.41up to date
 tracing-subscriber^0.3.170.3.19up to date
 url^2.4.12.5.4up to date
 x509-cert^0.2.40.2.5up to date
 zeroize^1.6.01.8.1up to date

Dev dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 hyper^0.14.271.6.0out of date
 indoc^2.0.42.0.5up to date
 openssl ⚠️^0.10.590.10.70maybe insecure
 temp-dir^0.1.110.1.14up to date
 tower^0.4.130.5.2out 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.

openssl: ssl::select_next_proto use after free

RUSTSEC-2025-0004

In openssl versions before 0.10.70, ssl::select_next_proto can return a slice pointing into the server argument's buffer but with a lifetime bound to the client argument. In situations where the server buffer's lifetime is shorter than the client buffer's, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client.

openssl 0.10.70 fixes the signature of ssl::select_next_proto to properly constrain the output buffer's lifetime to that of both input buffers.

In standard usage of ssl::select_next_proto in the callback passed to SslContextBuilder::set_alpn_select_callback, code is only affected if the server buffer is constructed within the callback. For example:

Not vulnerable - the server buffer has a 'static lifetime:

builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(b"\x02h2", client_protos).ok_or_else(AlpnError::NOACK)
});

Not vulnerable - the server buffer outlives the handshake:

let server_protos = b"\x02h2".to_vec();
builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(&server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});

Vulnerable - the server buffer is freed when the callback returns:

builder.set_alpn_select_callback(|_, client_protos| {
    let server_protos = b"\x02h2".to_vec();
    ssl::select_next_proto(&server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});