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, 26 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.98up to date
 base64^0.210.22.1out of date
 bytes^11.10.1up to date
 clap^34.5.37out of date
 cocoa^0.240.26.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.35up to date
 flate2^1.01.1.1up to date
 futures-util^0.30.3.31up to date
 glib^0.150.20.9out of date
 glob^0.30.3.2up to date
 gtk^0.150.18.2out of date
 http^0.21.3.1out of date
 ico^0.2.00.4.0out of date
 ignore^0.40.4.23up to date
 infer^0.90.19.0out of date
 minisign-verify^0.20.2.3up to date
 notify-rust^4.54.11.7up to date
 objc^0.20.2.7up to date
 once_cell^11.21.3up to date
 open^3.25.3.2out of date
 os_info^33.10.0up to date
 os_pipe^1.01.2.1up to date
 percent-encoding^2.22.3.1up to date
 png^0.170.17.16up to date
 rand^0.80.9.1out of date
 raw-window-handle^0.50.6.2out of date
 regex^1.6.01.11.1up to date
 reqwest^0.110.12.15out of date
 rfd^0.100.15.3out of date
 semver^1.01.0.26up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 serde_repr^0.10.1.20up to date
 serialize-to-javascript=0.1.10.1.2out of date
 shared_child^1.01.0.2up to date
 state^0.50.6.0out of date
 sys-locale^0.2.30.3.2out of date
 tar^0.4.380.4.44up to date
 tauri-macros^1.4.12.2.0out of date
 tauri-runtime^0.14.12.6.0out of date
 tauri-runtime-wry^0.14.12.6.0out of date
 tauri-utils^1.5.02.4.0out of date
 tempfile^33.19.1up to date
 thiserror^1.02.0.12out of date
 time^0.30.3.41up to date
 tokio ⚠️^11.45.0maybe insecure
 url^2.32.5.4up to date
 uuid^11.16.0up to date
 webkit2gtk^0.18.22.0.1out of date
 webview2-com^0.19.10.37.0out of date
 win7-notifications^0.40.4.5up to date
 windows^0.39.00.61.1out of date
 zip^0.62.6.1out of date

Dev dependencies

(9 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cargo_toml^0.110.22.1out of date
 mockito^0.311.7.0out of date
 proptest^1.0.01.6.0up to date
 quickcheck^1.0.31.0.3up to date
 quickcheck_macros^1.0.01.1.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 tokio ⚠️^11.45.0maybe insecure
 tokio-test^0.4.20.4.4up 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);