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

(32 total, 13 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.82.4.1out of date
 async-native-tls^0.40.5.0out of date
 async-net^1.72.0.0out of date
 async-std^11.13.1up to date
 async-trait^0.10.1.88up to date
 asynchronous-codec^0.60.7.0out of date
 bigdecimal^0.30.4.8out of date
 byteorder^1.01.5.0up to date
 bytes^1.01.10.1up to date
 chrono ⚠️^0.40.4.41maybe insecure
 connection-string^0.20.2.0up to date
 encoding_rs^0.80.8.35up to date
 enumflags2^0.70.7.12up to date
 futures-lite^1.12.02.6.0out of date
 futures-util^0.30.3.31up to date
 libgssapi^0.4.50.9.1out of date
 num-traits^0.20.2.19up to date
 once_cell^1.31.21.3up to date
 opentls^0.2.10.2.1up to date
 pin-project-lite^0.20.2.16up to date
 pretty-hex^0.30.4.1out of date
 rust_decimal^1.61.37.2up to date
 rustls-native-certs^0.60.8.1out of date
 rustls-pemfile^12.2.0out of date
 thiserror^1.02.0.12out of date
 time^0.30.3.41up to date
 tokio ⚠️^1.01.46.1maybe insecure
 tokio-rustls^0.24.00.26.2out of date
 tokio-util^0.70.7.15up to date
 tracing^0.10.1.41up to date
 uuid^1.01.17.0up to date
 winauth^0.0.40.0.5out of date

Dev dependencies

(15 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 async-std^11.13.1up to date
 azure_identity^0.5.00.25.0out of date
 chrono^0.4.380.4.41up to date
 env_logger^0.90.11.8out of date
 indicatif^0.170.18.0out of date
 indoc^1.0.72.0.6out of date
 names^0.140.14.0up to date
 oauth2^4.2.35.0.0out of date
 paste^1.01.0.15up to date
 reqwest^0.11.100.12.22out of date
 tokio ⚠️^1.01.46.1maybe insecure
 tokio-util^0.70.7.15up to date
 url^2.2.22.5.4up to date
 uuid^1.01.17.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

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