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 tauri

Dependencies

(56 total, 24 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.86up to date
 attohttpc^0.220.28.0out of date
 base64^0.210.22.1out of date
 bytes^11.6.1up to date
 clap^34.5.9out of date
 cocoa^0.240.25.0out of date
 data-url^0.20.3.1out of date
 dirs-next^2.02.0.0up to date
 embed_plist^1.21.2.2up to date
 encoding_rs^0.8.310.8.34up to date
 flate2^1.01.0.30up to date
 futures-util^0.30.3.30up to date
 glib^0.150.20.0out of date
 glob^0.30.3.1up to date
 gtk^0.150.18.1out of date
 http^0.21.1.0out of date
 ico^0.2.00.3.0out of date
 ignore=0.4.180.4.22out of date
 infer^0.90.16.0out of date
 minisign-verify^0.20.2.1up to date
 notify-rust^4.54.11.0up to date
 objc^0.20.2.7up to date
 once_cell^11.19.0up to date
 open^3.25.3.0out of date
 os_info^33.8.2up to date
 os_pipe^1.01.2.0up to date
 percent-encoding^2.22.3.1up to date
 png^0.170.17.13up to date
 rand^0.80.8.5up to date
 raw-window-handle=0.5.00.6.2out of date
 regex^1.6.01.10.5up to date
 reqwest^0.110.12.5out of date
 rfd^0.100.14.1out of date
 semver^1.01.0.23up to date
 serde^1.01.0.204up to date
 serde_json^1.01.0.120up to date
 serde_repr^0.10.1.19up to date
 serialize-to-javascript=0.1.10.1.1up to date
 shared_child^1.01.0.0up to date
 state^0.50.6.0out of date
 tar^0.4.380.4.41up to date
 tauri-macros^1.3.01.4.5up to date
 tauri-runtime^0.13.00.14.4out of date
 tauri-runtime-wry^0.13.00.14.9out of date
 tauri-utils^1.3.01.6.0up to date
 tempfile^33.10.1up to date
 thiserror^1.01.0.63up to date
 time=0.3.150.3.36out of date
 tokio ⚠️^11.38.1maybe insecure
 url^2.32.5.2up to date
 uuid^11.10.0up to date
 webkit2gtk^0.18.22.0.1out of date
 webview2-com^0.19.10.31.0out of date
 win7-notifications^0.3.10.4.4out of date
 windows^0.39.00.58.0out of date
 zip^0.62.1.3out of date

Dev dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cargo_toml^0.110.20.3out of date
 mockito^0.311.4.0out of date
 proptest^1.0.01.5.0up to date
 quickcheck^1.0.31.0.3up to date
 quickcheck_macros^1.0.01.0.0up to date
 serde^1.01.0.204up to date
 serde_json^1.01.0.120up to date
 tokio ⚠️^11.38.1maybe insecure
 tokio-test^0.4.20.4.4up to date
 winnow=0.4.10.6.13out of 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);