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 gtk-qq

Dependencies

(10 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.18.21.44.1maybe insecure
 rand^0.8.50.9.0out of date
 async-trait^0.1.530.1.88up to date
 once_cell^1.11.01.21.1up to date
 rusqlite^0.27.00.34.0out of date
 reqwest^0.11.100.12.15out of date
 qrcode-png^0.4.00.4.1up to date
 typed-builder^0.100.21.0out of date
 bincode^1.3.32.0.1out of date
 base64^0.13.00.22.1out of date

Crate widgets

Dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 typed-builder^0.100.21.0out of date

Crate resource-loader

Dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 serde^11.0.219up to date
 once_cell^1.111.21.1up to date
 derivative^2.22.2.0up to date
 log^0.40.4.26up to date
 tokio ⚠️^11.44.1maybe insecure
 tempfile^3.33.19.1up to date
 toml^0.5.90.8.20out of date
 tap^11.0.1up to date
 rand^0.8.50.9.0out of date
 directories^46.0.0out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^11.0.140up to date

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