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 sqlx-core

Dependencies

(51 total, 7 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.8.70.8.11up to date
 async-io^1.9.02.3.2out of date
 async-std^1.121.12.0up to date
 atoi^2.02.0.0up to date
 bigdecimal^0.3.00.4.3out of date
 bit-vec^0.6.30.6.3up to date
 bstr^1.01.9.1up to date
 byteorder^1.4.31.5.0up to date
 bytes^1.1.01.6.0up to date
 chrono ⚠️^0.4.190.4.38maybe insecure
 crc^33.2.1up to date
 crossbeam-queue^0.3.20.3.11up to date
 digest^0.10.00.10.7up to date
 either^1.6.11.11.0up to date
 encoding_rs^0.8.300.8.34up to date
 event-listener^2.5.25.3.0out of date
 futures-channel^0.3.190.3.30up to date
 futures-core^0.3.190.3.30up to date
 futures-intrusive^0.5.00.5.0up to date
 futures-io^0.3.240.3.30up to date
 futures-util^0.3.190.3.30up to date
 hashlink^0.8.00.9.0out of date
 hex^0.4.30.4.3up to date
 indexmap^2.02.2.6up to date
 ipnetwork^0.20.00.20.0up to date
 log^0.4.140.4.21up to date
 mac_address^1.1.51.1.6up to date
 memchr^2.4.12.7.2up to date
 native-tls^0.2.100.2.11up to date
 num-bigint^0.4.00.4.4up to date
 once_cell^1.9.01.19.0up to date
 paste^1.0.61.0.14up to date
 percent-encoding^2.1.02.3.1up to date
 regex^1.5.51.10.4up to date
 rust_decimal^1.26.11.35.0up to date
 rustls ⚠️^0.21.70.23.5out of date
 rustls-pemfile^1.02.1.2out of date
 serde^1.0.1321.0.199up to date
 serde_json^1.0.731.0.116up to date
 sha1^0.10.10.10.6up to date
 sha2^0.10.00.10.8up to date
 smallvec^1.7.01.13.2up to date
 sqlformat^0.2.00.2.3up to date
 thiserror^1.0.301.0.59up to date
 time^0.3.140.3.36up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-stream^0.1.80.1.15up to date
 tracing^0.1.370.1.40up to date
 url^2.2.22.5.0up to date
 uuid^1.1.21.8.0up to date
 webpki-roots^0.250.26.1out of date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 sqlx=0.7.40.7.4up to date
 tokio ⚠️^11.37.0maybe insecure

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

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.