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-cql

Dependencies

(15 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.570.1.83up to date
 bigdecimal^0.2.00.4.6out of date
 byteorder^1.3.41.5.0up to date
 bytes^1.0.11.8.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 lz4_flex^0.9.20.11.3out of date
 num-bigint^0.30.4.6out of date
 num_enum^0.50.7.3out of date
 scylla-macros^0.2.00.6.0out of date
 secrecy^0.7.00.10.3out of date
 serde^1.01.0.214up to date
 snap^1.01.1.1up to date
 thiserror^1.02.0.0out of date
 tokio ⚠️^1.121.41.1maybe insecure
 uuid^1.01.11.0up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.30.5.1out of 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);