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 tiberius

Dependencies

(29 total, 11 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-native-tls^0.30.5.0out of date
 async-std^11.13.0up to date
 async-stream^0.20.3.6out of date
 async-trait^0.10.1.83up to date
 asynchronous-codec^0.50.7.0out of date
 bigdecimal^0.2.00.4.5out of date
 byteorder^1.01.5.0up to date
 bytes^1.01.8.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 connection-string^0.1.40.2.0out of date
 encoding^0.20.2.33up to date
 enumflags2^0.70.7.10up to date
 futures^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 libgssapi^0.4.50.8.1out of date
 num-bigint^0.3.00.4.6out of date
 num-traits^0.20.2.19up to date
 once_cell^1.31.20.2up to date
 opentls^0.2.10.2.1up to date
 pin-project-lite^0.20.2.14up to date
 pretty-hex^0.10.4.1out of date
 rust_decimal^1.61.36.0up to date
 thiserror^1.01.0.65up to date
 tokio ⚠️^1.01.41.0maybe insecure
 tokio-util^0.60.7.12out of date
 tracing^0.10.1.40up to date
 uuid^0.81.11.0out of date
 winauth^0.0.40.0.5out of date

Dev dependencies

(6 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.91up to date
 async-std^11.13.0up to date
 env_logger^0.70.11.5out of date
 names^0.110.14.0out of date
 tokio ⚠️^1.01.41.0maybe insecure
 tokio-util^0.60.7.12out 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);