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 scylla-proxy

Dependencies

(13 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bigdecimal^0.2.00.4.6out of date
 byteorder^1.3.41.5.0up to date
 bytes^1.2.01.8.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 futures^0.3.60.3.31up to date
 num-bigint^0.30.4.6out of date
 num_enum^0.50.7.3out of date
 rand^0.8.50.8.5up to date
 scylla-cql^0.0.70.3.0out of date
 thiserror^1.0.322.0.0out of date
 tokio ⚠️^1.121.41.1maybe insecure
 tracing^0.1.250.1.40up to date
 uuid^1.01.11.0up to date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 env_logger^0.90.11.5out of date
 ntest^0.8.10.9.3out of date
 tracing-subscriber^0.3.140.3.18up 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

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