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 turso

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.11.01.11.0up to date
 http-body-util^0.1.30.1.3up to date
 hyper^1.8.11.8.1up to date
 hyper-tls^0.6.00.6.0up to date
 hyper-util^0.1.190.1.19up to date
 mimalloc^0.1.470.1.48up to date
 thiserror^2.0.162.0.18up to date
 tokio ⚠️^1.01.49.0maybe insecure
 tracing^0.1.410.1.44up to date
 tracing-subscriber^0.3.200.3.22up to date
 turso_sdk_kit^0.4.40.4.4up to date
 turso_sync_sdk_kit^0.4.40.4.4up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.981.0.100up to date
 rand^0.9.20.9.2up to date
 rand_chacha^0.9.00.9.0up to date
 reqwest^0.12.280.13.1out of date
 serde_json^1.01.0.149up to date
 tempfile^3.20.03.24.0up to date
 tokio ⚠️^1.01.49.0maybe insecure

Security Vulnerabilities

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