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

Dependencies

(16 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.521.0.98up to date
 backoff^0.4.00.4.0up to date
 cargo_metadata^0.18.10.21.0out of date
 chrono ⚠️^0.4.190.4.41maybe insecure
 clap^4.3.104.5.43up to date
 clap_complete^4.3.14.5.55up to date
 console^0.15.00.16.0out of date
 dialoguer^0.110.11.0up to date
 dotenvy^0.15.00.15.7up to date
 filetime^0.20.2.25up to date
 futures^0.3.190.3.31up to date
 glob^0.3.00.3.2up to date
 openssl ⚠️^0.10.380.10.73maybe insecure
 serde_json^1.0.731.0.142up to date
 sqlx=0.8.60.8.6up to date
 tokio ⚠️^1.15.01.47.1maybe insecure

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 assert_cmd^2.0.112.0.17up to date
 tempfile^3.10.13.20.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);

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.