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, 12 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.82.3.3out of date
 async-native-tls^0.40.5.0out of date
 async-net^1.72.0.0out of date
 async-std^11.12.0up to date
 async-trait^0.10.1.80up to date
 asynchronous-codec^0.60.7.0out of date
 bigdecimal^0.30.4.5out of date
 byteorder^1.01.5.0up to date
 bytes^1.01.6.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 connection-string^0.20.2.0up to date
 encoding^0.20.2.33up to date
 enumflags2^0.70.7.10up to date
 futures-lite^1.12.02.3.0out of date
 futures-util^0.30.3.30up to date
 libgssapi^0.4.50.7.2out of date
 num-traits^0.20.2.19up to date
 once_cell^1.31.19.0up to date
 opentls^0.2.10.2.1up to date
 pin-project-lite^0.20.2.14up to date
 pretty-hex^0.30.4.1out of date
 rust_decimal^1.61.35.0up to date
 rustls-native-certs^0.60.7.1out of date
 rustls-pemfile^12.1.2out of date
 thiserror^1.01.0.61up to date
 time^0.30.3.36up to date
 tokio ⚠️^1.01.38.0maybe insecure
 tokio-rustls^0.23.30.26.0out of date
 tokio-util^0.70.7.11up to date
 tracing^0.10.1.40up to date
 uuid^1.01.9.1up to date
 winauth^0.0.40.0.5out of date

Dev dependencies

(15 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.86up to date
 async-std^11.12.0up to date
 azure_identity^0.5.00.20.0out of date
 chrono ⚠️^0.40.4.38maybe insecure
 env_logger^0.90.11.3out of date
 indicatif^0.170.17.8up to date
 indoc^1.0.72.0.5out of date
 names^0.140.14.0up to date
 oauth2^4.2.34.4.2up to date
 paste^1.01.0.15up to date
 reqwest^0.11.100.12.5out of date
 tokio ⚠️^1.01.38.0maybe insecure
 tokio-util^0.70.7.11up to date
 url^2.2.22.5.2up to date
 uuid^1.01.9.1up 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);