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.

Crate leaf

Dependencies

(63 total, 6 outdated, 5 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.37.0maybe insecure
 protobuf=3.4.03.4.0up to date
 thiserror^1.01.0.59up to date
 futures^0.30.3.30up to date
 async-trait^0.10.1.80up to date
 bytes^1.61.6.0up to date
 lazy_static^1.41.4.0up to date
 anyhow^1.01.0.82up to date
 rand^0.80.8.5up to date
 socket2^0.50.5.7up to date
 async-recursion^1.11.1.1up to date
 trust-dns-proto^0.230.23.2up to date
 lru^0.120.12.3up to date
 tracing^0.10.1.40up to date
 tracing-appender^0.20.2.3up to date
 tracing-subscriber^0.30.3.18up to date
 chrono ⚠️^0.40.4.38maybe insecure
 colored^2.12.1.0up to date
 maxminddb^0.240.24.0up to date
 memmap2^0.90.9.4up to date
 cidr^0.20.2.2up to date
 directories^4.05.0.1out of date
 async-ffi^0.20.5.0out of date
 libloading^0.70.8.3out of date
 serde_json^1.01.0.116up to date
 serde_derive^1.01.0.200up to date
 serde^1.01.0.200up to date
 regex^1.101.10.4up to date
 openssl ⚠️^0.100.10.64maybe insecure
 ring^0.170.17.8up to date
 aws-lc-rs^1.71.7.0up to date
 tokio-rustls^0.260.26.0up to date
 webpki-roots^0.250.26.1out of date
 rustls-pemfile^1.02.1.2out of date
 openssl-probe^0.10.1.5up to date
 tokio-openssl^0.60.6.4up to date
 tungstenite^0.210.21.0up to date
 tokio-tungstenite^0.210.21.0up to date
 url^2.52.5.0up to date
 http^1.11.1.0up to date
 async-socks5^0.60.6.0up to date
 hkdf^0.120.12.4up to date
 md-5^0.100.10.6up to date
 sha-1^0.100.10.1up to date
 percent-encoding^2.32.3.1up to date
 base64^0.220.22.1up to date
 memchr^22.7.2up to date
 sha2^0.100.10.8up to date
 hex^0.40.4.3up to date
 lz_fnv^0.10.1.2up to date
 cfb-mode^0.80.8.2up to date
 hmac^0.120.12.1up to date
 aes^0.80.8.4up to date
 sha3^0.100.10.8up to date
 digest^0.100.10.7up to date
 uuid^11.8.0up to date
 byteorder^11.5.0up to date
 lru_time_cache^0.110.11.11up to date
 tokio-util^0.70.7.10up to date
 quinn^0.100.10.2up to date
 rustls ⚠️^0.210.23.5out of date
 warp ⚠️^0.30.3.7maybe insecure
 notify^66.1.1up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 rcgen^0.130.13.1up to date
 sha2^0.100.10.8up to date
 tokio ⚠️^11.37.0maybe insecure

Build dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.01.0.96up to date
 bindgen^0.690.69.4up to date
 protobuf-codegen=3.4.03.4.0up to date

Crate leaf-cli

Dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.37.0maybe insecure
 argh^0.10.1.12up to date

Crate leaf-ffi

No external dependencies! 🙌

Crate shadowsocks

Dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.80up to date
 tokio ⚠️^11.37.0maybe insecure
 async-ffi^0.20.5.0out of date
 bytes^11.6.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

warp: Improper validation of Windows paths could lead to directory traversal attack

RUSTSEC-2022-0082

Path 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 corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If 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.