This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
leaf(63 total, 16 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio ⚠️ | ^1 | 1.43.0 | maybe insecure |
| protobuf | =3.6.0 | 3.7.1 | out of date |
| thiserror | ^1.0 | 2.0.11 | out of date |
| futures | ^0.3 | 0.3.31 | up to date |
| async-trait | ^0.1 | 0.1.86 | up to date |
| bytes | ^1.6 | 1.10.0 | up to date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| anyhow | ^1.0 | 1.0.95 | up to date |
| rand | ^0.8 | 0.9.0 | out of date |
| socket2 | ^0.5 | 0.5.8 | up to date |
| async-recursion | ^1.1 | 1.1.1 | up to date |
| trust-dns-proto | ^0.23 | 0.23.2 | up to date |
| lru | ^0.12 | 0.13.0 | out of date |
| tracing | ^0.1 | 0.1.41 | up to date |
| tracing-appender | ^0.2 | 0.2.3 | up to date |
| tracing-subscriber | ^0.3 | 0.3.19 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.39 | maybe insecure |
| colored | ^2.1 | 3.0.0 | out of date |
| maxminddb | ^0.24 | 0.24.0 | up to date |
| memmap2 | ^0.9 | 0.9.5 | up to date |
| cidr | ^0.2 | 0.3.1 | out of date |
| directories | ^4.0 | 6.0.0 | out of date |
| async-ffi | ^0.2 | 0.5.0 | out of date |
| libloading | ^0.7 | 0.8.6 | out of date |
| serde_json | ^1.0 | 1.0.138 | up to date |
| serde_derive | ^1.0 | 1.0.217 | up to date |
| serde | ^1.0 | 1.0.217 | up to date |
| regex | ^1.10 | 1.11.1 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.70 | maybe insecure |
| ring | ^0.17 | 0.17.8 | up to date |
| aws-lc-rs | ^1.7 | 1.12.2 | up to date |
| tokio-rustls | ^0.26 | 0.26.1 | up to date |
| webpki-roots | ^0.25 | 0.26.8 | out of date |
| rustls-pemfile | ^1.0 | 2.2.0 | out of date |
| openssl-probe | ^0.1 | 0.1.6 | up to date |
| tokio-openssl | ^0.6 | 0.6.5 | up to date |
| tungstenite | ^0.21 | 0.26.1 | out of date |
| tokio-tungstenite | ^0.21 | 0.26.1 | out of date |
| url | ^2.5 | 2.5.4 | up to date |
| http | ^1.1 | 1.2.0 | up to date |
| async-socks5 | ^0.6 | 0.6.0 | up to date |
| hkdf | ^0.12 | 0.12.4 | up to date |
| md-5 | ^0.10 | 0.10.6 | up to date |
| sha-1 | ^0.10 | 0.10.1 | up to date |
| percent-encoding | ^2.3 | 2.3.1 | up to date |
| base64 | ^0.22 | 0.22.1 | up to date |
| memchr | ^2 | 2.7.4 | up to date |
| sha2 | ^0.10 | 0.10.8 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| lz_fnv | ^0.1 | 0.1.2 | up to date |
| cfb-mode | ^0.8 | 0.8.2 | up to date |
| hmac | ^0.12 | 0.12.1 | up to date |
| aes | ^0.8 | 0.8.4 | up to date |
| sha3 | ^0.10 | 0.10.8 | up to date |
| digest | ^0.10 | 0.10.7 | up to date |
| uuid | ^1 | 1.13.1 | up to date |
| byteorder | ^1 | 1.5.0 | up to date |
| lru_time_cache | ^0.11 | 0.11.11 | up to date |
| tokio-util | ^0.7 | 0.7.13 | up to date |
| quinn | ^0.10 | 0.11.6 | out of date |
| rustls ⚠️ | ^0.21 | 0.23.22 | out of date |
| warp ⚠️ | ^0.3 | 0.3.7 | maybe insecure |
| notify | ^6 | 8.0.0 | out of date |
(3 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rcgen | ^0.13 | 0.13.2 | up to date |
| sha2 | ^0.10 | 0.10.8 | up to date |
| tokio ⚠️ | ^1 | 1.43.0 | maybe insecure |
(3 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| cc | ^1.0 | 1.2.13 | up to date |
| bindgen | ^0.69 | 0.71.1 | out of date |
| protobuf-codegen | =3.6.0 | 3.7.1 | out of date |
leaf-cli(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio ⚠️ | ^1 | 1.43.0 | maybe insecure |
| argh | ^0.1 | 0.1.13 | up to date |
leaf-ffiNo external dependencies! 🙌
shadowsocks(4 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1 | 0.1.86 | up to date |
| tokio ⚠️ | ^1 | 1.43.0 | maybe insecure |
| async-ffi | ^0.2 | 0.5.0 | out of date |
| bytes | ^1 | 1.10.0 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
warp: Improper validation of Windows paths could lead to directory traversal attackPath resolution in warp::filters::fs::dir didn't correctly validate Windows paths
meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed
and respond with the contents of c:/windows/web/screen/img101.png. Thus users
could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
openssl: ssl::select_next_proto use after freeIn 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)
});